Comparison Overview
Nagarro + MBIS
Nagarro + MBIS
Cevizli Mah. Tugay yolu Cad., İstanbul, 34846, TR
Last Update: 21/05/2026
With a strong legacy in information technologies in Türkiye, MBIS became part of Nagarro—a global digital engineering company—in 2023. This combination brought together local expertise with global experience and an engineering-driven culture, opening a new chapter of gr...
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
Nagarro + MBIS
Amadeus
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Nagarro + MBIS in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Amadeus in 2026.
Incident History - Nagarro + MBIS (X = Date, Y = Severity)
Nagarro + MBIS 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
Nagarro + MBIS
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.