Comparison Overview
HCA Healthcare
HCA Healthcare
1 Park Plaza, Nashville, TN, US, 37203
Last Update: 13/09/2026
HCA Healthcare is dedicated to giving people a healthier tomorrow. As one of the nation’s leading providers of healthcare services, HCA Healthcare is comprised of 189 hospitals and approximately 2,600 sites of care in 19 states and the United Kingdom. In addition to h...
RHÖN-KLINIKUM AG
1 Schlossplatz, Bad Neustadt an der Saale, DE, 97616
Last Update: 07/09/2026
Die RHÖN‐KLINIKUM AG ist einer der größten Gesundheitsdienstleister in Deutschland. Die Kliniken bieten exzellente Medizin mit direkter Anbindung zu Universitäten und Forschungseinrichtungen. An den fünf Standorten Campus Bad Neustadt, Klinikum Frankfurt (Oder), Univers...
Compliance Ranges Comparison
HCA Healthcare
RHÖN-KLINIKUM AG
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for HCA Healthcare in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for RHÖN-KLINIKUM AG in 2026.
Incident History - HCA Healthcare (X = Date, Y = Severity)
HCA Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Incident History - RHÖN-KLINIKUM AG (X = Date, Y = Severity)
RHÖN-KLINIKUM AG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
HCA Healthcare
RHÖN-KLINIKUM AG
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.