Comparison Overview
Infora GmbH
Infora GmbH
Konrad-Adenauer-Str. 13, Köln, Nordrhein-Westfalen, 50996 , DE
Last Update: 21/02/2026
Mit bedarfsgerechten und modularen Vorgehensmodellen unterstützen wir die öffentlichen Verwaltung bei der Digitalisierung nachhaltig. In zahlreichen Erfolgsprojekten auf allen Verwaltungsebenen und einem hohen Maß an Individualität für Ihre Anforderungen sind wir der Pa...
Conduent
100 Campus Dr, Florham Park, 07932, US
Last Update: 11/09/2026
Conduent delivers digital business solutions and services spanning the commercial, government and transportation spectrum – creating valuable outcomes for its clients and the millions of people who count on them. We leverage cloud computing, artificial intelligence, mac...
Compliance Ranges Comparison
Infora GmbH
Conduent
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Infora GmbH in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
Conduent has 773.79% more incidents than the average of all companies with at least one recorded incident.
Incident History - Infora GmbH (X = Date, Y = Severity)
Infora GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Conduent (X = Date, Y = Severity)
Conduent cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Infora GmbH
Conduent
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.