Comparison Overview
ExxonMobil Fawley
ExxonMobil Fawley
Marsh Lane, Fawley, SO45 1TX, GB
Last Update: 01/04/2026
The ExxonMobil Fawley complex is the largest of its kind in the UK, employing over 2,500 staff and valued contractors. We produce one fifth of the fuel used on the country's roads; and a range of important chemicals used in everyday life.
CB&I
1725 Hughes Landing Blvd, The Woodlands, 77380, US
Last Update: 03/04/2026
CB&I is the world’s leading designer and builder of storage facilities, tanks, and terminals. With more than 60,000 structures completed throughout its 135+ year history, CB&I has the global expertise and strategically located operations to provide its customers world-c...
Compliance Ranges Comparison
ExxonMobil Fawley
CB&I
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for ExxonMobil Fawley in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for CB&I in 2026.
Incident History - ExxonMobil Fawley (X = Date, Y = Severity)
ExxonMobil Fawley cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CB&I (X = Date, Y = Severity)
CB&I cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ExxonMobil Fawley
CB&I
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: *.*.