Comparison Overview
Grow @ Nagarro
Grow @ Nagarro
N/A
Last Update: 28/03/2026
This page is your inside look at what it’s like to be a Nagarrian. You’ll find stories of bold ideas, inclusive culture, real career journeys, learning moments, and the little things that make us who we are. From real stories to behind-the-scenes snapshots, it’s all her...
Capita
2 Kingdom Street, First Floor, London, England, GB, W2 6BD
Last Update: 15/09/2026
Capita is an outsourcer, helping clients across the public and private sectors run complex business processes more efficiently, creating better consumer experiences. Operating across eight countries, Capita’s 34,000 colleagues support primarily UK and European clients ...
Compliance Ranges Comparison
Grow @ Nagarro
Capita
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Grow @ Nagarro in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Capita in 2026.
Incident History - Grow @ Nagarro (X = Date, Y = Severity)
Grow @ Nagarro cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Capita (X = Date, Y = Severity)
Capita cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Grow @ Nagarro
Capita
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.