Comparison Overview
BlueCherry®
BlueCherry®
200 Vesey Street, None, New York, New York, US, 100080
Last Update: 25/06/2026
BlueCherry® Enterprise Suite delivers comprehensive digital supply chain management solutions. With a focus on high-growth organizations operating in consumer lifestyle products, retail and apparel, BlueCherry is a unified SaaS platform that provides supply chain visibi...
Wolt
Pohjoinen Rautatiekatu 21, Helsinki, Uusimaa, FI, 00100
Last Update: 15/09/2026
Wolt is a Helsinki-based technology company with a mission to bring joy, simplicity and earnings to the neighborhoods of the world. Wolt develops a local commerce platform that connects people looking to order food, groceries, and other goods with people interested in s...
Compliance Ranges Comparison
BlueCherry®
Wolt
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for BlueCherry® in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Wolt in 2026.
Incident History - BlueCherry® (X = Date, Y = Severity)
BlueCherry® cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Wolt (X = Date, Y = Severity)
Wolt cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BlueCherry®
Wolt
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.