Comparison Overview
INEOS Grangemouth

INEOS Grangemouth
Bo'ness Road, Grangemouth, Stirlingshire, FK3 9XH, GB
Last Update: 01/05/2026
Located at Grangemouth, some 40km west of Edinburgh, one of INEOS’ largest manufacturing sites directly employs c2000 highly skilled people. The 1700 acre site is home to Scotland’s only crude oil refinery (producing the bulk of fuels used in northern Britain) as well a...

Brenntag
Messeallee 11, Essen , 45131, DE
Last Update: 01/04/2026
Brenntag is the global market leader in chemicals and ingredients distribution and holds a central role in connecting customers and suppliers of the chemical industry. Headquartered in Essen, Germany, we have more than 18,100 employees worldwide and operate a network of...
Compliance Ranges Comparison

INEOS Grangemouth







Brenntag






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

INEOS Grangemouth

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