Comparison Overview
ExxonMobil Baytown Area
ExxonMobil Baytown Area
Baytown, US
Last Update: 26/03/2026
Founded in 1919, the Baytown Refinery began operation in 1920 and the Chemical Plant started up in 1940. The complex is located on approximately 3,400 acres along the Houston Ship Channel, about 25 miles east of Houston. It is comprised of four manufacturing sites, inc...
Chevron
1400 Smith St, Houston, Texas, US, 77002
Last Update: 07/10/2026
Our greatest resource is our people. Their ingenuity, creativity and collaboration have met the complex challenges of energy’s past. Together, we’ll take on the future. We support the LinkedIn Terms of Use (User Agreement), and we expect visitors to our page to do the ...
Compliance Ranges Comparison
ExxonMobil Baytown Area
Chevron
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for ExxonMobil Baytown Area in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
Chevron has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - ExxonMobil Baytown Area (X = Date, Y = Severity)
ExxonMobil Baytown Area cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Chevron (X = Date, Y = Severity)
Chevron cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ExxonMobil Baytown Area
Chevron
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.