Comparison Overview
Deutsche Telekom IT
Deutsche Telekom IT
N/A
Last Update: 17/12/2025
Welcome to Deutsche Telekom IT! Who are we? We are Deutsche Telekom's IT company of choice, uniting over 9,100 top experts from 65 nationalities across six countries to bring the future to telecommunications. Driven by this shared purpose, we deliver superior digi...
Lenovo
8001 Development Dr, Morrisville, 27560, US
Last Update: 01/09/2026
Lenovo is a US$83 billion revenue global technology powerhouse, ranked #196 in the Fortune Global 500, and serving millions of customers every day in 180 markets. Guided by its vision of “Smarter Technology for All”, Lenovo is executing a Hybrid AI strategy that spans P...
Compliance Ranges Comparison
Deutsche Telekom IT
Lenovo
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Deutsche Telekom IT in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Lenovo has 191.26% more incidents than the average of all companies with at least one recorded incident.
Incident History - Deutsche Telekom IT (X = Date, Y = Severity)
Deutsche Telekom IT cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lenovo (X = Date, Y = Severity)
Lenovo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Deutsche Telekom IT
Lenovo
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.