Comparison Overview
ibis, ibis Styles, ibis budget
ibis, ibis Styles, ibis budget
N/A
Last Update: 23/04/2026
In September 1974, our first hotel opened its doors, marking the beginning of an incredible journey in hospitality. Over the years, ibis has become one of the world's leading economy brands, offering unforgettable stays and experiences. With 2500 hotels in 79 countries...
Accor
82 rue Henri Farman, Issy-les-Moulineaux, Paris Region, FR, 92130
Last Update: 19/09/2026
We are Accor We are more than 290,000 hospitality experts placing people at the heart of what we do, creating emotion for our guests, and nurturing passion for service and achievement beyond limits. Building on the strength of our teams and of our fully integrated ecos...
Compliance Ranges Comparison
ibis, ibis Styles, ibis budget
Accor
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for ibis, ibis Styles, ibis budget in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Accor in 2026.
Incident History - ibis, ibis Styles, ibis budget (X = Date, Y = Severity)
ibis, ibis Styles, ibis budget cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Accor (X = Date, Y = Severity)
Accor cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ibis, ibis Styles, ibis budget
Accor
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.