Comparison Overview
Digital at BT Group
Digital at BT Group
1 Braham Street, London, England, E1 8EE, GB
Last Update: 06/03/2026
BT Group's future is based on us bringing innovative solutions to market, fast. Partnering with our customers and suppliers, we're delivering innovative, adaptable solutions over best-in-class digital platforms. Digital’s role is to drive all elements of that equation,...
Capgemini
Place de l'Étoile, Paris, 75017, FR
Last Update: 14/09/2026
Capgemini is an AI-powered global business and technology transformation partner, delivering tangible business value. We imagine the future of organizations and make it real with AI, technology and people. With our strong heritage of nearly 60 years, we are a responsibl...
Compliance Ranges Comparison
Digital at BT Group
Capgemini
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Digital at BT Group in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Capgemini in 2026.
Incident History - Digital at BT Group (X = Date, Y = Severity)
Digital at BT Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Capgemini (X = Date, Y = Severity)
Capgemini cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Digital at BT Group
Capgemini
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.