Comparison Overview
Atlantic Oceanographic and Meteorological Laboratory (AOML)
Atlantic Oceanographic and Meteorological Laboratory (AOML)
undefined, Miami, FL, undefined, US
Last Update: 25/10/2025
NOAA's Atlantic Oceanographic and Meteorological Laboratory (AOML) is a federal research lab in Miami, Florida. As part of NOAA's Office of Oceanic and Atmospheric Research, we study hurricanes, coastal ecosystems, oceans and human health, climate, global carbon, and ho...
UK Home Office
2 Marsham Street, London, GB, SW1P 4DF
Last Update: 30/04/2026
At the Home Office, we help to ensure that the country is safe and secure. We’ve been looking after UK citizens since 1782. We are responsible for: - working on the problems caused by illegal drug use - shaping the alcohol strategy, policy and licensing conditions - k...
Compliance Ranges Comparison
Atlantic Oceanographic and Meteorological Laboratory (AOML)
UK Home Office
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Atlantic Oceanographic and Meteorological Laboratory (AOML) in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for UK Home Office in 2026.
Incident History - Atlantic Oceanographic and Meteorological Laboratory (AOML) (X = Date, Y = Severity)
Atlantic Oceanographic and Meteorological Laboratory (AOML) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UK Home Office (X = Date, Y = Severity)
UK Home Office cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Atlantic Oceanographic and Meteorological Laboratory (AOML)
UK Home Office
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: *.*.