Comparison Overview
Autogrill
Autogrill
Palazzo Z Strada 5, Rozzano - Milanofiori, Italy, 20089, IT
Last Update: 23/04/2026
Autogrill is the world’s leading provider of food & beverage services for travellers. The Group is present in 30 countries on 4 continents, operates in about 774 locations managing about 3,300 points of sale with about 46,000 employees and is present in 139 airports. A...
The Cheesecake Factory
26901 Malibu Hills Road, Calabasas Hills, CA, US, 91301
Last Update: 11/09/2026
We're known for our huge restaurants and generous portions but we're so much more than that! Here, you'll have big opportunities to learn and grow your career, you can take pride in the work you do, be able to balance your life with the hours and schedule you need, and ...
Compliance Ranges Comparison
Autogrill
The Cheesecake Factory
Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Autogrill in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for The Cheesecake Factory in 2026.
Incident History - Autogrill (X = Date, Y = Severity)
Autogrill cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The Cheesecake Factory (X = Date, Y = Severity)
The Cheesecake Factory cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Autogrill
The Cheesecake Factory
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.