Comparison Overview
Mercuri Urval Norway
Mercuri Urval Norway
Sjølyst plass 2, Oslo, 0278, NO
Last Update: 04/12/2025
Mercuri Urval Norway, part of Mercuri Urval, a leading Global Consultancy with over 800 professionals operating in 70 offices in 24 countries world wide. We align key people to the strategic needs of our clients. We work with you to identify, develop and acquire the cap...
ERM
33 St Mary Axe, London, GB, EC3A 8AA
Last Update: 02/04/2026
Sustainability is our business. As the world’s largest specialist sustainability consultancy, ERM partners with clients to operationalize sustainability at pace and scale, deploying a unique combination of strategic transformation and technical delivery capabilities....
Compliance Ranges Comparison
Mercuri Urval Norway
ERM
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Mercuri Urval Norway in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for ERM in 2026.
Incident History - Mercuri Urval Norway (X = Date, Y = Severity)
Mercuri Urval Norway cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ERM (X = Date, Y = Severity)
ERM cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Mercuri Urval Norway
ERM
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: *.*.