Comparison Overview
Frito-Lay
Frito-Lay
7701 Legacy Dr, Plano, 75024, US
Last Update: 13/09/2026
We believe every consumer should have access to their favorite snack, everywhere. We own the manufacturing process from seed to shelf and actively invest in technology to automate key steps of the process. This helps us be more agile in what we need to make, who we need...
Dairy Queen
8331 Norman Center Dr, Bloomington, 55437, US
Last Update: 14/09/2026
Here at the DQ® system, we believe that HAPPY TASTES GOOD®. Our first location opened in Joliet, Illinois, 80 years ago. Since then we’ve grown to more than 7,000 DQ® locations in the U.S., Canada and 22 other countries. Our restaurants offer a variety of sweet trea...
Compliance Ranges Comparison
Frito-Lay
Dairy Queen
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Frito-Lay in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Dairy Queen in 2026.
Incident History - Frito-Lay (X = Date, Y = Severity)
Frito-Lay cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dairy Queen (X = Date, Y = Severity)
Dairy Queen cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Frito-Lay
Dairy Queen
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.