Comparison Overview
Cat Oil & Gas
Cat Oil & Gas
10203 Sam Houston Park Dr, Houston, Texas, 77064, US
Last Update: 06/02/2026
You know Caterpillar for construction and mining equipment, but did you know we also help power the global energy industry? Since the 1930s, we’ve been helping companies bring oil and gas to the world as cleanly, reliably and cost-effectively as possible. Today, we serv...
Oxy
Houston, 77046, US
Last Update: 11/09/2026
Oxy is an international energy company that produces, markets and transports oil and natural gas to maximize value and provide resources fundamental to life. The company leverages its global leadership in carbon management to advance lower-carbon technologies and produc...
Compliance Ranges Comparison
Cat Oil & Gas
Oxy
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Cat Oil & Gas in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Oxy in 2026.
Incident History - Cat Oil & Gas (X = Date, Y = Severity)
Cat Oil & Gas cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Oxy (X = Date, Y = Severity)
Oxy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Cat Oil & Gas
Oxy
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.