Comparison Overview
T-Systems Iberia
T-Systems Iberia
Carrer de Pere IV, 313, Barcelona, 08019, ES
Last Update: 02/04/2026
En T-Systems, encontrarás proyectos rompedores que suman al bienestar social y ecológico. Queremos dar la bienvenida a nuevos talentos como tú, que aporten ideas frescas, puntos de vista distintos, que acepten retos y un continuo aprendizaje, para crecer e impactar a la...
Verizon
One Verizon Way, Basking Ridge, 07920-1097, US
Last Update: 14/09/2026
We get you. You want more out of a career. A place to share your ideas freely — even if they’re daring or different. Where the true you can learn, grow, and thrive. You’ll find all that here. Because we empower you. We power and empower how people live, work and play ...
Compliance Ranges Comparison
T-Systems Iberia
Verizon
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for T-Systems Iberia in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Verizon has 579.61% more incidents than the average of all companies with at least one recorded incident.
Incident History - T-Systems Iberia (X = Date, Y = Severity)
T-Systems Iberia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Verizon (X = Date, Y = Severity)
Verizon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
T-Systems Iberia
Verizon
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.