Comparison Overview
OPEC
OPEC
Helferstorferstrasse 17, Vienna, 1010, AT
Last Update: 01/04/2026
OFFICIAL ACCOUNT OPEC is a permanent intergovernmental Organization of 12 oil-exporting countries: Algeria, Congo, Equatorial Guinea, Gabon, IR Iran, Iraq, Kuwait, Libya, Nigeria, Saudi Arabia, the UAE and Venezuela. The Organization was established in Iraq at the Firs...
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
OPEC
PEMEX
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for OPEC in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for PEMEX in 2026.
Incident History - OPEC (X = Date, Y = Severity)
OPEC 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
OPEC
PEMEX
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.