Comparison Overview
Procter & Gamble Pakistan
Procter & Gamble Pakistan
The Harbour Front, Karachi, 75000, PK
Last Update: 27/12/2025
Being the world’s largest consumer goods company, we are home to one of the strongest portfolios of trusted, quality, leadership brands, including Always®, Ambi Pur®, Ariel®, Downy®, Dynamo®, Febreze®, Gillette®, Head & Shoulders®, Olay®, Oral-B®, Pampers®, Pantene®, Sa...
Unilever
100 Victoria Embankment, Blackfriars, London, GB, EC4Y 0DY
Last Update: 31/05/2026
Every day, 3.4 billion people around the world enjoy our products - from ground-breaking brands like Hellmann's, Domestos, Dove and Rexona (to name just a few). Our brands lead the way - innovating in their fields, delighting their consumers and powering our business fo...
Compliance Ranges Comparison
Procter & Gamble Pakistan
Unilever
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Procter & Gamble Pakistan in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Unilever in 2026.
Incident History - Procter & Gamble Pakistan (X = Date, Y = Severity)
Procter & Gamble Pakistan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Unilever (X = Date, Y = Severity)
Unilever cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Procter & Gamble Pakistan
Unilever
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: *.*.