Comparison Overview
ExxonMobil Pipeline Company

ExxonMobil Pipeline Company
Spring, 77389, US
Last Update: 29/12/2025
ExxonMobil Pipeline Company LLC, an indirectly wholly owned subsidiary of Exxon Mobil Corporation, and its affiliates are working to meet the world’s energy needs AND taking steps to help reduce greenhouse gas emissions. We transport crude oil, refined products, liquefi...

PEMEX
Marina Nacional #329,, México, 11311, MX
Last Update: 18/09/2026
Petróleos Mexicanos es la mayor empresa de México, el mayor contribuyente fiscal del país, así como una de las empresas más grandes de América Latina. Es de las pocas empresas petroleras del mundo que desarrolla toda la cadena productiva de la industria, desde la exp...
Compliance Ranges Comparison

ExxonMobil Pipeline Company







PEMEX






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

ExxonMobil Pipeline Company

PEMEX
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.