Comparison Overview
KPMG Emerging Giants (NL)
KPMG Emerging Giants (NL)
Laan van Langerhuize 1, Amstelveen, Noord Holland, NL, 1186
Last Update: 27/02/2026
KPMG Emerging Giants supports scaleups in their growth and international expansion. We understand what it takes for fast-growing companies to be successful in each stage of their business journey, and with our dedicated team of experts, we provide hands-on support wh...
ELIS
18, Rue Hoche, Puteaux, 92800, FR
Last Update: 01/04/2026
As the leader in circular services at work, Elis ensures its clients achieve optimal hygiene, well-being and protection – everywhere, every day, in a sustainable way. We employ 54,000 people locally in 30 countries. We work for public and private organizations of all s...
Compliance Ranges Comparison
KPMG Emerging Giants (NL)
ELIS
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for KPMG Emerging Giants (NL) in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for ELIS in 2026.
Incident History - KPMG Emerging Giants (NL) (X = Date, Y = Severity)
KPMG Emerging Giants (NL) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ELIS (X = Date, Y = Severity)
ELIS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
KPMG Emerging Giants (NL)
ELIS
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.