Comparison Overview
Programa da ONU para o Meio Ambiente
Programa da ONU para o Meio Ambiente
-, Brasília, BR
Last Update: 23/01/2026
Conta oficial do Programa das Nações Unidas para o Meio Ambiente no Brasil.
World Health Organization
20, avenue Appia, Geneva 27, 1211, CH
Last Update: 02/04/2026
The World Health Organization's mission: to promote health, keep the world safe, and serve the vulnerable. Working through offices in more than 150 countries, WHO staff work side by side with governments and other partners to ensure the highest attainable level of healt...
Compliance Ranges Comparison
Programa da ONU para o Meio Ambiente
World Health Organization
Benchmark & Cyber Underwriting Signals
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for Programa da ONU para o Meio Ambiente in 2026.
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for World Health Organization in 2026.
Incident History - Programa da ONU para o Meio Ambiente (X = Date, Y = Severity)
Programa da ONU para o Meio Ambiente cyber incidents detection timeline including parent company and subsidiaries.
Incident History - World Health Organization (X = Date, Y = Severity)
World Health Organization cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Programa da ONU para o Meio Ambiente
World Health Organization
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: *.*.