Comparison Overview
Agile Hub T-Systems Iberia
Agile Hub T-Systems Iberia
Calle de Sancho de Ávila, 120, Barcelona, 08018, ES
Last Update: 27/02/2026
🔭 En Agile Hub T-Systems Iberia vivimos nuestra visión cada día: Nos adaptamos al cambio, reaccionando más rápidamente a la situación del mercado, somos un proveedor de referencia ágil para nuestros clientes y habilitamos que T-Systems sea un gran lugar para trabajar.....
Amadeus
C/Salvador de Madariaga 1, Madrid, 28027, ES
Last Update: 17/09/2026
We make the experience of travel better for everyone, everywhere by inspiring innovation, partnerships and responsibility to people, places and planet. Our technology powers the travel and tourism industry. We inspire more connected ways of thinking, centered around ...
Compliance Ranges Comparison
Agile Hub T-Systems Iberia
Amadeus
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Agile Hub T-Systems Iberia in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Amadeus in 2026.
Incident History - Agile Hub T-Systems Iberia (X = Date, Y = Severity)
Agile Hub T-Systems Iberia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amadeus (X = Date, Y = Severity)
Amadeus cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Agile Hub T-Systems Iberia
Amadeus
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.