Comparison Overview
Soundcraft

Soundcraft
Cranbourne Road, Potters Bar, Herts, EN6 3JN, GB
Last Update: 02/02/2026
Soundcraft designs and manufactures analog and digital audio mixing consoles for live, theater, AV, and recording applications. Founded in 1973, Soundcraft first made its mark with the launch of the Series 1, the first mixing console in a flightcase. Today, Soundcraf...

Eaton
30 Pembroke Road, Dublin, Ireland, IE, 4
Last Update: 01/04/2026
Eaton is an intelligent power management company dedicated to improving the quality of life and protecting the environment for people everywhere. We are guided by our commitment to do business right, to operate sustainably and to help our customers manage power ─ today ...
Compliance Ranges Comparison

Soundcraft







Eaton






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

Soundcraft

Eaton
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.