Comparison Overview
Maroma, A Belmond Hotel
Maroma, A Belmond Hotel
Carretera Cancún-Tulum, Km 51, Riviera Maya, 77710, MX
Last Update: 23/03/2026
A secret haven awaits, blending Mayan traditions with refined vitality. This enchanting resort offers a secluded location between 200 acres of jungle and one of the best natural beaches in Mexico. Recently transformed, this secluded hideaway captivates with the sights, ...
TUI
Karl-Wiechert Allee 23, Hannover, 30625, DE
Last Update: 08/09/2026
We’re adventure seekers. Smile givers. Impact makers. We believe in the power of travel. It broadens horizons for our customers, and for our people too. New places to live, new roles to explore, new communities to join. It’s yours for the taking. We’re TUI, a leading...
Compliance Ranges Comparison
Maroma, A Belmond Hotel
TUI
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Maroma, A Belmond Hotel in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for TUI in 2026.
Incident History - Maroma, A Belmond Hotel (X = Date, Y = Severity)
Maroma, A Belmond Hotel cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TUI (X = Date, Y = Severity)
TUI cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Maroma, A Belmond Hotel
TUI
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.