Comparison Overview
Climate Program Office
Climate Program Office
1315 East West Hwy, Silver Spring, 20910, US
Last Update: 09/02/2026
The Climate Program Office (CPO) manages competitive research programs in which NOAA funds high-priority climate science, assessments, decision support research, outreach, education, and capacity-building activities designed to advance our understanding of Earth’s clima...
Swiss Federal Administration
Eigerstrasse 71, Bern, 3003, CH
Last Update: 03/04/2026
Seven departments, the Federal Chancellery and around 70 administrative units make up the Federal Administration. With around 38,000 employees, we are one of the largest employers in Switzerland. Everyone who works for the Federal Administration actively contributes t...
Compliance Ranges Comparison
Climate Program Office
Swiss Federal Administration
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Climate Program Office in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Swiss Federal Administration in 2026.
Incident History - Climate Program Office (X = Date, Y = Severity)
Climate Program Office cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Swiss Federal Administration (X = Date, Y = Severity)
Swiss Federal Administration cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Climate Program Office
Swiss Federal Administration
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: *.*.