Comparison Overview
Pakistan Petroleum Limited
Pakistan Petroleum Limited
PIDC House, Karachi, PK
Last Update: 30/03/2026
The pioneer of the natural gas industry in the country, Pakistan Petroleum Limited (PPL) has been a frontline player in the energy sector since the mid-1950s. As a major supplier of natural gas, PPL today contributes over 20 percent of the country’s total natural gas su...
Equinor
Forusbeen 50, Stavanger, Rogaland, NO, 4035
Last Update: 05/07/2026
We're Equinor, an international energy company with a proud history. Formerly Statoil, we are 20,000 committed colleagues developing oil, gas, wind and solar energy in more than 30 countries worldwide. We’re the largest operator in Norway, among the world’s largest offs...
Compliance Ranges Comparison
Pakistan Petroleum Limited
Equinor
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Pakistan Petroleum Limited in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Equinor in 2026.
Incident History - Pakistan Petroleum Limited (X = Date, Y = Severity)
Pakistan Petroleum Limited cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Equinor (X = Date, Y = Severity)
Equinor cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pakistan Petroleum Limited
Equinor
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: *.*.