Comparison Overview
Kent
Kent
Office 2501, Swiss Tower, JLT Cluster Y, Dubai, undefined, 27062, AE
Last Update: 17/03/2026
We design, build and maintain the assets that power the world for today and make it future-ready for tomorrow. From consulting to design, build, commissioning and start-up through to maintenance and decommissioning. It is our ambition to become the global leader in...
Capgemini Engineering
76, Avenue Kléber, Paris, 75116, FR
Last Update: 14/09/2026
Capgemini Engineering is the engineering and R&D services powerhouse of the Capgemini Group, combining its broad industry knowledge and cutting-edge technologies in digital and software to support the convergence of the physical and digital worlds. Coupled with the capa...
Compliance Ranges Comparison
Kent
Capgemini Engineering
Benchmark & Cyber Underwriting Signals
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for Kent in 2026.
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for Capgemini Engineering in 2026.
Incident History - Kent (X = Date, Y = Severity)
Kent cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Capgemini Engineering (X = Date, Y = Severity)
Capgemini Engineering cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Kent
Capgemini Engineering
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.