Comparison Overview
Comfort Hotels
Comfort Hotels
1 Choice Hotels Cir, Rockville, 20850, US
Last Update: 30/01/2026
The Comfort® brand family, including Comfort Inn®, Comfort Inn & Suites®, and Comfort Suites®, features a modern look and amenities designed to help you feel refreshed and ready to take on the day. We offer a consistent, warm and welcoming experience with benefits that ...
Aramark
2400 Market St, Philadelphia, 19103, US
Last Update: 05/09/2026
Aramark (NYSE: ARMK) proudly serves the world’s leading educational institutions, Fortune 500 companies, world champion sports teams, prominent healthcare providers, iconic destinations and cultural attractions, and numerous municipalities in 16 countries around the wor...
Compliance Ranges Comparison
Comfort Hotels
Aramark
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Comfort Hotels in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Aramark in 2026.
Incident History - Comfort Hotels (X = Date, Y = Severity)
Comfort Hotels cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aramark (X = Date, Y = Severity)
Aramark cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Comfort Hotels
Aramark
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.