Comparison Overview
Chefkoch GmbH
Chefkoch GmbH
undefined, Bonn, NRW, 53227, DE
Last Update: 25/02/2026
Chefkoch begeistert mit mehr als 350.000 Rezepten monatlich bis zu 22 Mio. Nutzer:innen. Damit ist Chefkoch Europas größte Food-Plattform und zählt zu den reichweitenstärksten Onlineportalen in Deutschland. Die Chefkoch GmbH ist Teil von RTL Deutschland, Unternehmensbe...
Zomato
Pioneer Square, Gurugram, 122101, IN
Last Update: 13/09/2026
Zomato’s mission statement is “better food for more people.” Since our inception in 2010, we have grown tremendously, both in scope and scale - and emerged as India’s most trusted brand during the pandemic, along with being one of the largest hyperlocal delivery network...
Compliance Ranges Comparison
Chefkoch GmbH
Zomato
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Chefkoch GmbH in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Zomato in 2026.
Incident History - Chefkoch GmbH (X = Date, Y = Severity)
Chefkoch GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Zomato (X = Date, Y = Severity)
Zomato cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Chefkoch GmbH
Zomato
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.