Comparison Overview

ExxonMobil

VS

PDVSA Petróleos de Venezuela S.A.

ExxonMobil

US
Last Update: 2026-04-01
View Profile
Between 800 and 849
http://www.exxonmobil.com

The need for energy is universal. That's why ExxonMobil scientists and engineers are pioneering new research and pursuing new technologies to reduce emissions while creating more efficient fuels. We're committed to responsibly meeting the world's energy needs. We aim to achieve #netzero emissions from our operated assets by 2050 (for Scope 1 and 2 greenhouse gas emissions) and are taking a comprehensive approach to create emission-reduction roadmaps for major operated assets. Find us also on: YouTube.com/ExxonMobil Find our latest Privacy Policy at https://corporate.exxonmobil.com/Global-legal-pages/privacy-policy See our terms and conditions at https://corporate.exxonmobil.com/global-legal-pages/terms-and-conditions Find resources on our GHG emission reduction efforts here: https://corporate.exxonmobil.com/resources

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 66,908
Subsidiaries: 37
12-month incidents
0
Known data breaches
1
Attack type number
1
View Profile

PDVSA Petróleos de Venezuela S.A.

Avenida. Libertador con calle El Empalme , Caracas, 1050, VE
Last Update: 2026-04-03
Between 650 and 699
https://www.pdvsa.com

Petróleos de Venezuela S.A. is a Venezuelan state company, began operations on January 1st, 1976 and whose activities are the oil exploration, production, refining, marketing and transportation of Venezuelan oil as well as the orimulsion, chemical, petrochemical businesses and coal. We have the largest oil reserves in the world, reaching at the end of 2013, a total certified sum of 298,353 million barrels, which represent 20% of the world reserves of this resource. Also we manage 197.1 trillion cubic feet of natural gas in proven reserves, a figure that places us in eighth place worldwide. PDVSA carries out its crude processing operations through 14 refineries: six in Venezuela, and nine in the rest of the world. The national refining system is made up of 6 refineries that have a processing capacity of 1 million 303 MBD of which 52% is destined for the local market and 48% for export. The international refining system is made up of 9 refineries located in the Caribbean region, United States and Europe. Our subsidiaries and affiliates are located across the globe in Venezuela, Belgium, China, Dominican Republic, Netherlands, Sweden, the United Kingdom and the United States. Headquartered in Caracas, Venezuela, with offices and operations throughout the country, we employ more than 140,000 workers worldwide.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 25,708
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/exxonmobil.jpeg
ExxonMobil
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/petroleosdevenezuela.jpeg
PDVSA Petróleos de Venezuela S.A.
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
ExxonMobil
100%
Compliance Rate
0/4 Standards Verified
PDVSA Petróleos de Venezuela S.A.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for ExxonMobil in 2026.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for PDVSA Petróleos de Venezuela S.A. in 2026.

Incident History — ExxonMobil (X = Date, Y = Severity)

ExxonMobil cyber incidents detection timeline including parent company and subsidiaries

Incident History — PDVSA Petróleos de Venezuela S.A. (X = Date, Y = Severity)

PDVSA Petróleos de Venezuela S.A. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/exxonmobil.jpeg
ExxonMobil
Incidents

Date Detected: 12/2024
Type:Breach
Motivation: To protect corporate interests amid environmental scrutiny
Blog: Blog
https://images.rankiteo.com/companyimages/petroleosdevenezuela.jpeg
PDVSA Petróleos de Venezuela S.A.
Incidents

Date Detected: 12/2025
Type:Cyber Attack
Blog: Blog

Date Detected: 12/2025
Type:Cyber Attack
Motivation: Sabotage/Disruption of operations
Blog: Blog

Date Detected: 11/2025
Type:Breach
Attack Vector: Internal Misconduct
Motivation: New Card Solicitation (Non-Malicious)
Blog: Blog

FAQ

ExxonMobil company demonstrates a stronger AI Cybersecurity Score compared to PDVSA Petróleos de Venezuela S.A. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

PDVSA Petróleos de Venezuela S.A. company has faced a higher number of disclosed cyber incidents historically compared to ExxonMobil company.

In the current year, PDVSA Petróleos de Venezuela S.A. company and ExxonMobil company have not reported any cyber incidents.

PDVSA Petróleos de Venezuela S.A. company has confirmed experiencing a ransomware attack, while ExxonMobil company has not reported such incidents publicly.

Both PDVSA Petróleos de Venezuela S.A. company and ExxonMobil company have disclosed experiencing at least one data breach.

PDVSA Petróleos de Venezuela S.A. company has reported targeted cyberattacks, while ExxonMobil company has not reported such incidents publicly.

Neither ExxonMobil company nor PDVSA Petróleos de Venezuela S.A. company has reported experiencing or disclosing vulnerabilities publicly.

Neither ExxonMobil nor PDVSA Petróleos de Venezuela S.A. holds any compliance certifications.

Neither company holds any compliance certifications.

ExxonMobil company has more subsidiaries worldwide compared to PDVSA Petróleos de Venezuela S.A. company.

ExxonMobil company employs more people globally than PDVSA Petróleos de Venezuela S.A. company, reflecting its scale as a Oil and Gas.

Neither ExxonMobil nor PDVSA Petróleos de Venezuela S.A. holds SOC 2 Type 1 certification.

Neither ExxonMobil nor PDVSA Petróleos de Venezuela S.A. holds SOC 2 Type 2 certification.

Neither ExxonMobil nor PDVSA Petróleos de Venezuela S.A. holds ISO 27001 certification.

Neither ExxonMobil nor PDVSA Petróleos de Venezuela S.A. holds PCI DSS certification.

Neither ExxonMobil nor PDVSA Petróleos de Venezuela S.A. holds HIPAA certification.

Neither ExxonMobil nor PDVSA Petróleos de Venezuela S.A. holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References