Comparison Overview
Hello Cake
Hello Cake
Los Angeles , CA, US
Last Update: 03/04/2026
Hello Cake is on a mission to help couples reconnect in the bedroom. Through our line of specialty lubricants, supplements, toys and prescription medication, we're proudly a wellness brand for the sexually active. Hello Cake is a brand within the SWG Brands portfolio....
Whirlpool Corporation
2000 North M63, Benton Harbor, Michigan, US, 49022
Last Update: 13/09/2026
Life at home has been at the heart of our business for 110+ years - it is why we exist and why we are passionate about what we do. Beginning with our founders to the everyday actions of our people, our values have always kept us grounded -- Integrity, Respect, Inclusion...
Compliance Ranges Comparison
Hello Cake
Whirlpool Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Hello Cake in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Whirlpool Corporation in 2026.
Incident History - Hello Cake (X = Date, Y = Severity)
Hello Cake cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Whirlpool Corporation (X = Date, Y = Severity)
Whirlpool Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hello Cake
Whirlpool Corporation
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.