Comparison Overview
Emanuel Medical Center
Emanuel Medical Center
825 Delbon Ave, Turlock, 95382, US
Last Update: 02/04/2026
At Emanuel Medical Center, our family of nurses, doctors, staff and healthcare specialists are dedicated to providing expert, compassionate care for all the families of Turlock and the surrounding communities. We’ve been caring for you and your loved ones since 1917 — ...
Hapvida NotreDame Intermédica
Av. Paulista 867, São Paulo, 01311-100, BR
Last Update: 05/09/2026
Com 80 anos de experiência, a Hapvida é hoje a maior empresa de saúde integrada da América Latina. A companhia, que possui mais de 73 mil colaboradores, atende 16 milhões de beneficiários de saúde e odontologia espalhados pelas cinco regiões do Brasil. Todo o aparato ...
Compliance Ranges Comparison
Emanuel Medical Center
Hapvida NotreDame Intermédica
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Emanuel Medical Center in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Hapvida NotreDame Intermédica in 2026.
Incident History - Emanuel Medical Center (X = Date, Y = Severity)
Emanuel Medical Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hapvida NotreDame Intermédica (X = Date, Y = Severity)
Hapvida NotreDame Intermédica cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Emanuel Medical Center
Hapvida NotreDame Intermédica
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.