Comparison Overview
Optum Philippines

Optum Philippines
N/A
Last Update: 25/08/2026
The local subsidiary of Optum Global Solutions under UnitedHealth Group. Optum Philippines is a Global Capability Center (GCC) providing technology, clinical, and customer service solutions in support of the company’s worldwide operations. Currently operating in Metro...

Akamai Technologies
8 Cambridge Center, Cambridge, 02142, US
Last Update: 15/09/2026
At Akamai, we make life better for billions of people, billions of times a day. Every day, billions of people around the world connect with their favorite brands to shop online, play the latest video games, log into mobile banking apps, learn remotely, share videos wi...
Compliance Ranges Comparison

Optum Philippines







Akamai Technologies






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Optum Philippines in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
Akamai Technologies has 191.26% more incidents than the average of all companies with at least one recorded incident.
Incident History - Optum Philippines (X = Date, Y = Severity)
Optum Philippines cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Akamai Technologies (X = Date, Y = Severity)
Akamai Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Optum Philippines

Akamai Technologies
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.