Comparison Overview
Sony Electronics

Sony Electronics
16535 Via Esprillo, San Diego - US | Tokyo - JP, US
Last Update: 12/03/2026
WE ARE SONY Our spirit of innovation and challenge has created those special moments that make people say ‘wow’. How? By harnessing the world’s most powerful source of creativity: our people. Because ‘wow’ experiences are never a product of processes or procedures. T...

Garmin
1200 E. 151st Street, Olathe, KS, US, 66062
Last Update: 10/09/2026
WHERE DO WE START? How about Kansas City? That’s our home. That’s where Garmin put a stake in the ground in 1989. We’ve grown substantially over the years, offering diverse products and global reach in 5 diverse markets. But some things won’t ever change: Our entreprene...
Compliance Ranges Comparison

Sony Electronics







Garmin






Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Sony Electronics in 2026.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
Garmin has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Sony Electronics (X = Date, Y = Severity)
Sony Electronics cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Garmin (X = Date, Y = Severity)
Garmin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sony Electronics

Garmin
FAQ
Latest Global CVEs
The web management service in affected RouterOS versions contains an integer underflow in its HTTP request body handling that is reachable before authentication. This can be leveraged by an unauthenticated network attacker to achieve arbitrary code execution as root, or to cause a denial of service, using a single crafted request.
Denuvo Anti-Tamper through 2026-03-04 allows bypass of a hypervisor presence check via CPUID interception (SimpleSvm.sys on AMD; hyperkd.sys and hyperhv.dll on Intel).
PeaZip before 11.3.0, in a non-default configuration, is vulnerable to OS command injection via a filename in an archive because "quotation character already used in the string" is mishandled.
Zilliz Attu before 3.0.0 has a Playground feature that does not require authentication for proxying arbitrary HTTP and HTTPS requests to URLs on the public internet.
The Playground feature of Zilliz Attu before 3.0.0 allows SSRF (proxying of requests to private IP addresses).