Comparison Overview
Next Haskoning
Next Haskoning
Rüdigerstrasse 15, None, Zürich, Zürich, CH, 8045
Last Update: 01/11/2025
Do you want to build a data centre or mission-critical facility that can handle any challenge? By partnering with Next, you will benefit from the expertise of an energetic team of architects and engineers who specialise in designing the most advanced and complex project...
Petrofac
117 Jermyn Street, London, GB, SW1Y 6HH
Last Update: 29/03/2026
We are a leading international service provider to the energy industry, with a diverse client portfolio including many of the world’s leading energy companies. Petrofac designs, builds, manages and maintains oil, gas, refining, petrochemicals and renewable energy infra...
Compliance Ranges Comparison
Next Haskoning
Petrofac
Benchmark & Cyber Underwriting Signals
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for Next Haskoning in 2026.
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for Petrofac in 2026.
Incident History - Next Haskoning (X = Date, Y = Severity)
Next Haskoning cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Petrofac (X = Date, Y = Severity)
Petrofac cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Next Haskoning
Petrofac
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: *.*.