Comparison Overview
Intermountain Health
Intermountain Health
5245 South College Drive, Murray , UT, US, 84123
Last Update: 13/09/2026
Headquartered in Utah with locations in six primary states and additional operations across the western U.S., Intermountain Health is a nonprofit system of 34 hospitals, 400+ clinics, a medical group of more than 4,800 employed physicians and advanced care providers, a ...
Cincinnati Children's
US
Last Update: 31/03/2026
Cincinnati Children’s, a nonprofit academic medical center established in 1883, offers services from well-child care to treatment for the most rare and complex conditions. It is the Department of Pediatrics at the University of Cincinnati College of Medicine and trains ...
Compliance Ranges Comparison
Intermountain Health
Cincinnati Children's
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Intermountain Health in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Cincinnati Children's in 2026.
Incident History - Intermountain Health (X = Date, Y = Severity)
Intermountain Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cincinnati Children's (X = Date, Y = Severity)
Cincinnati Children's cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Intermountain Health
Cincinnati Children's
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.