Comparison Overview
NASEM Climate
NASEM Climate
500 5th St NW, Washington, 20001, US
Last Update: 10/01/2026
The National Academies of Sciences, Engineering, and Medicine (NASEM) plays a crucial role in shaping and influencing climate policy and research in the United States and around the world. Climate Crossroads is the National Academies’ sustained and comprehensive appro...
The Salvation Army
615 Slaters, Alexandria, VA, US, 22314
Last Update: 04/04/2026
The Salvation Army is the nation's largest direct provider of social services. Annually, we help millions overcome poverty, addiction, and spiritual and economic hardships by preaching the gospel of Jesus Christ and meeting human needs in His name without discriminati...
Compliance Ranges Comparison
NASEM Climate
The Salvation Army
Benchmark & Cyber Underwriting Signals
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for NASEM Climate in 2026.
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for The Salvation Army in 2026.
Incident History - NASEM Climate (X = Date, Y = Severity)
NASEM Climate cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The Salvation Army (X = Date, Y = Severity)
The Salvation Army cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NASEM Climate
The Salvation Army
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.