Comparison Overview
PAHO Procurement and Supply Management
PAHO Procurement and Supply Management
525 23rd St NW, Washington, 20037, US
Last Update: 23/03/2026
The Procurement and Supply Management Department (PRO) is committed to ensuring access to services and strategic products to achieve better health in the Americas. PRO provides effective and value-added procurement to support the delivery of public health goods and ser...
UNESCO
7 Place de Fontenoy, Paris, 75007, FR
Last Update: 03/04/2026
UNESCO - the United Nations Educational, Scientific and Cultural Organization (UNESCO) was founded on 16 November 1945. For this specialized United Nations agency, it is not enough to build classrooms in devastated countries or to publish scientific breakthroughs. Educa...
Compliance Ranges Comparison
PAHO Procurement and Supply Management
UNESCO
Benchmark & Cyber Underwriting Signals
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for PAHO Procurement and Supply Management in 2026.
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for UNESCO in 2026.
Incident History - PAHO Procurement and Supply Management (X = Date, Y = Severity)
PAHO Procurement and Supply Management cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UNESCO (X = Date, Y = Severity)
UNESCO cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PAHO Procurement and Supply Management
UNESCO
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: *.*.