Comparison Overview
Chevron Technology Ventures

Chevron Technology Ventures
1500 Louisiana St, Houston, US
Last Update: 31/03/2026
Chevron Technology Ventures (CTV) supports business, technology and cultural innovation across Chevron. CTV was launched in 1999 to identify and integrate externally developed technologies and new business solutions with the potential to enhance the way Chevron produces...

CB&I
1725 Hughes Landing Blvd, The Woodlands, 77380, US
Last Update: 03/04/2026
CB&I is the world’s leading designer and builder of storage facilities, tanks, and terminals. With more than 60,000 structures completed throughout its 135+ year history, CB&I has the global expertise and strategically located operations to provide its customers world-c...
Compliance Ranges Comparison

Chevron Technology Ventures







CB&I






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

Chevron Technology Ventures

CB&I
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.