Comparison Overview
Petroleum Exploration Private Limited
Petroleum Exploration Private Limited
House # 20, Main Margalla Road, F-8/3, Islamabad, 44000, PK
Last Update: 09/11/2025
PEL is a private sector Pakistani E&P company. It was established in 1994 and in a short period has become an active operator having the largest acreage among ten private sector companies in Pakistan. It is exploring on land and deep waters off-shore Pakistan. It is als...
PEMEX
Marina Nacional #329,, México, 11311, MX
Last Update: 03/04/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
Petroleum Exploration Private Limited
PEMEX
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Petroleum Exploration Private Limited in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for PEMEX in 2026.
Incident History - Petroleum Exploration Private Limited (X = Date, Y = Severity)
Petroleum Exploration Private Limited 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
Petroleum Exploration Private Limited
PEMEX
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.