Comparison Overview
Outcomes®
Outcomes®
5900 Lake Ellenor Dr, Suite 600, Orlando, Florida, US, 32809
Last Update: 03/04/2026
Outcomes® unites technology and clinical relationships through a connected healthcare network to drive better outcomes. As a leading patient-centric technology business, we unite pharmacies, payers, and pharmaceutical companies through patient engagement solutions, tai...
Apollo Hospitals
Chennai, 600006, IN
Last Update: 13/09/2026
Driven by the vision of its Chairman, Dr. Prathap C. Reddy, the Apollo Hospitals Group pioneered corporate healthcare in India. Apollo revolutionized healthcare when Dr Prathap Reddy opened the first hospital in Chennai in 1983. Today Apollo is the world’s largest inte...
Compliance Ranges Comparison
Outcomes®
Apollo Hospitals
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Outcomes® in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Apollo Hospitals has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Outcomes® (X = Date, Y = Severity)
Outcomes® cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Apollo Hospitals (X = Date, Y = Severity)
Apollo Hospitals cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Outcomes®
Apollo Hospitals
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.