Comparison Overview
OIM México
OIM México
Calle Montes Urales 440, Miguel Hidalgo, Alcaldía Miguel Hidalgo, 11000, MX
Last Update: 13/12/2025
Más de 300 personas trabajamos en ONU Migración/OIM México. Desarrollamos una labor en 9 áreas de trabajo humanitario, fundamentalmente.
USAID
1300 Pennsylvania Ave NW, Washington, District of Columbia, US, 20004
Last Update: 30/08/2026
USAID is the lead U.S. Government agency that works to end extreme global poverty and enable resilient, democratic societies to realize their potential. U.S. foreign assistance has always had the twofold purpose of furthering America's interests while improving lives...
Compliance Ranges Comparison
OIM México
USAID
Benchmark & Cyber Underwriting Signals
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for OIM México in 2026.
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for USAID in 2026.
Incident History - OIM México (X = Date, Y = Severity)
OIM México cyber incidents detection timeline including parent company and subsidiaries.
Incident History - USAID (X = Date, Y = Severity)
USAID cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
OIM México
USAID
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.