Comparison Overview
OIM Costa Rica
OIM Costa Rica
Sigma Business Center, Costado Oeste del Mall San Pedro. Torre C, Piso 1. San Pedro, San José, Costa Rica, San José, CR
Last Update: 21/04/2026
Costa Rica se convirtió en miembro de la OIM en 1952, y la organización mantiene una oficina en el país desde 1954. La misión de la OIM en Costa Rica opera desde su oficina principal en San José y en lugares estratégicos asistiendo a personas migrantes en todo el país.
UNDP
1 United Nations Plaza, New York, 10017, US
Last Update: 01/04/2026
The United Nations Development Programme works in nearly 170 countries and territories, helping to achieve the eradication of poverty, and the reduction of inequalities and exclusion. We help countries to develop policies, leadership skills, partnering abilities, instit...
Compliance Ranges Comparison
OIM Costa Rica
UNDP
Benchmark & Cyber Underwriting Signals
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for OIM Costa Rica in 2026.
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for UNDP in 2026.
Incident History - OIM Costa Rica (X = Date, Y = Severity)
OIM Costa Rica cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UNDP (X = Date, Y = Severity)
UNDP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
OIM Costa Rica
UNDP
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: *.*.