Comparison Overview
Open Arms Care
Open Arms Care
7325 Oak Ridge Highway, Knoxville, 37931, US
Last Update: 12/06/2026
Our Mission: Supporting people with intellectual and developmental disabilities to reach their maximum potential and lead dignified and meaningful lives. Our Vision: The vision of Open Arms Care is being the recognized leader in providing innovative services for peo...
Health Care Service Corporation
300 E Randolph St, Chicago, 60601, US
Last Update: 11/09/2026
Health Care Service Corporation serves nearly 23 million people across the United States through its portfolio of health benefit solutions. HCSC provides health coverage options for employers large and small, individuals and families, and Medicare and Medicaid plans. H...
Compliance Ranges Comparison
Open Arms Care
Health Care Service Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Open Arms Care in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Health Care Service Corporation in 2026.
Incident History - Open Arms Care (X = Date, Y = Severity)
Open Arms Care cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Health Care Service Corporation (X = Date, Y = Severity)
Health Care Service Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Open Arms Care
Health Care Service Corporation
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.