Comparison Overview
Rakuten.ca
Rakuten.ca
4881 Yonge St, Toronto, Ontario, M2N 5X3, CA
Last Update: 29/04/2026
Rakuten.ca has helped its 7+ million members earn over $70 million in Cash Back. By connecting shoppers with top brands they already know and love, we provide Cash Back on everything from travel, luxury products, gift cards and everyday essentials, while our retail part...
Delivery Hero
Oranienburger Straße 70, Berlin, 10117, DE
Last Update: 13/09/2026
As the world’s pioneering local delivery platform, our mission is to deliver an amazing experience, fast, easy, and to your door. We operate in around 65 countries worldwide, powered by tech, designed by people. As one of Europe’s largest tech platforms, headquartered i...
Compliance Ranges Comparison
Rakuten.ca
Delivery Hero
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Rakuten.ca in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Delivery Hero in 2026.
Incident History - Rakuten.ca (X = Date, Y = Severity)
Rakuten.ca cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Delivery Hero (X = Date, Y = Severity)
Delivery Hero cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Rakuten.ca
Delivery Hero
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.