Comparison Overview
KoçDigital
KoçDigital
Ümraniye Sile Baglanti Yolu, Ümraniye, İstanbul, undefined, TR
Last Update: 30/12/2025
Digital is transforming business across all at an unprecedented pace today, presenting significant opportunities and challenges at the same time. Yet, many companies struggle in navigating this turbulent digital landscape. As KoçDigital to partner with our clients on th...
Serco
16 Bartley Wood Business Park, Bartley Way, Hook, RG27 9UY, GB
Last Update: 12/09/2026
We bring together the right people, the right technology and the right partners to create innovative solutions that make positive impact and address some of the most urgent and complex challenges facing the modern world. With a focus on serving governments globally, ...
Compliance Ranges Comparison
KoçDigital
Serco
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for KoçDigital in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Serco in 2026.
Incident History - KoçDigital (X = Date, Y = Severity)
KoçDigital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Serco (X = Date, Y = Severity)
Serco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
KoçDigital
Serco
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.