Comparison Overview
T-Systems Nederland B.V.
T-Systems Nederland B.V.
Van Deventerlaan 31-51, Utrecht, 3528 AG, NL
Last Update: 20/03/2026
Want to know us better? Subscribe for the T-Systems innovation & Tech Day 2025: https://info.t-systems.nl/innovation_and_tech_day_2025 T-Systems is een van Europa’s grootste ICT-dienstverleners. Als onderdeel van Deutsche Telekom, combineren we lokale klantfocus met in...
Nagarro
Munich, DE
Last Update: 31/03/2026
Nagarro helps future-proof your business through a forward-thinking, fluidic, and CARING mindset. We excel at digital engineering and help our clients become human-centric, digital-first organizations, augmenting their ability to be responsive, efficient, intimate, crea...
Compliance Ranges Comparison
T-Systems Nederland B.V.
Nagarro
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for T-Systems Nederland B.V. in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Nagarro in 2026.
Incident History - T-Systems Nederland B.V. (X = Date, Y = Severity)
T-Systems Nederland B.V. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Nagarro (X = Date, Y = Severity)
Nagarro cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
T-Systems Nederland B.V.
Nagarro
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.