Comparison Overview
Logitech

Logitech
3930 N 1st St, San Jose, California, US, 95134
Last Update: 02/04/2026
At Logitech, our purpose is to extend human potential in work and play. We do this by designing software-enabled hardware solutions that drive superior performance when gaming and superior productivity while at work, all with maximum comfort, speed and accuracy. We ena...

HARMAN International
400 Atlantic St, Stamford, 06901, US
Last Update: 02/04/2026
Headquartered in Stamford, Connecticut, HARMAN (harman.com) designs and engineers connected products and solutions for automakers, consumers, and enterprises worldwide, including connected car systems, audio and visual products, enterprise automation solutions; and serv...
Compliance Ranges Comparison

Logitech







HARMAN International






Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Logitech in 2026.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for HARMAN International in 2026.
Incident History - Logitech (X = Date, Y = Severity)
Logitech cyber incidents detection timeline including parent company and subsidiaries.
Incident History - HARMAN International (X = Date, Y = Severity)
HARMAN International cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Logitech

HARMAN International
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.