Comparison Overview
ExxonMobil Joliet

ExxonMobil Joliet
25915 S Frontage Rd, Channahon, 60410, US
Last Update: 01/03/2026
The Joliet Refinery is located 40 miles southwest of Chicago, Ill. Built in 1972, the Joliet facility is one of the newest refineries in the United States and is ideally located to receive and process Canadian crude oil delivered by pipeline. The characteristics of Cana...

PETRONAS
Kuala Lumpur, 50088, MY
Last Update: 03/04/2026
Petroliam Nasional Berhad (PETRONAS) is a leading global energy company committed to powering society’s progress in a responsible and sustainable manner. With close to 50,000 employees and a global reach spanning over 100 countries, we are ranked among the world’s large...
Compliance Ranges Comparison

ExxonMobil Joliet







PETRONAS






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for ExxonMobil Joliet in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for PETRONAS in 2026.
Incident History - ExxonMobil Joliet (X = Date, Y = Severity)
ExxonMobil Joliet cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PETRONAS (X = Date, Y = Severity)
PETRONAS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ExxonMobil Joliet

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