Comparison Overview
Dow MobilityScience

Dow MobilityScience
Midland, US
Last Update: 04/04/2026
The transportation industry is in the midst of its most significant transformation in over 100 years. Digital technologies and the pressing need for a low-carbon economy have disrupted traditional value chains. Demand for more connected, autonomous, shared, and electric...

INEOS
38 Hans Crescent, London, SW1X 0LZ, GB
Last Update: 01/04/2026
We are a global manufacturer of raw materials and a producer of energy used in everyday life. From medicines to mobile phones, agriculture to automotive, our products enhance standards of living for everyone around the world. We understand the challenge the world is f...
Compliance Ranges Comparison

Dow MobilityScience







INEOS






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

Dow MobilityScience

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