Comparison Overview
JW Marriott Bucharest Grand Hotel

JW Marriott Bucharest Grand Hotel
Calea 13 Septembrie 90, Bucharest, 050726, RO
Last Update: 25/01/2026
Located in an area of historic and national interest, JW Marriott Bucharest Grand Hotel in Romania is the only five-star, hotel in the district and is in close proximity to the stately Palace of Parliament and People’s Salvation Cathedral. Culturally rich and with a s...

Hilton
7930 Jones Branch Drive, McLean, 22102, US
Last Update: 14/09/2026
Hilton (NYSE: HLT) is a leading global hospitality company with a portfolio of 27 world-class brands comprising more than 9,100 properties and over 1.3 million rooms, in 143 countries and territories. Dedicated to fulfilling its founding vision to fill the earth with th...
Compliance Ranges Comparison

JW Marriott Bucharest Grand Hotel







Hilton






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for JW Marriott Bucharest Grand Hotel in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Hilton in 2026.
Incident History - JW Marriott Bucharest Grand Hotel (X = Date, Y = Severity)
JW Marriott Bucharest Grand Hotel cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hilton (X = Date, Y = Severity)
Hilton cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

JW Marriott Bucharest Grand Hotel

Hilton
FAQ
Latest Global CVEs
A vulnerability was determined in xuxueli xxl-job up to 3.5.0. The impacted element is an unknown function of the file /jobgroup/insert. This manipulation of the argument Name causes cross site scripting. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
A vulnerability was found in Moore Threads MTT S80 Driver Package 340.150. The affected element is the function sub_140006F0C in the library mtdispkm64.sys of the component IOCTL Handler. The manipulation results in improper privilege management. Attacking locally is a requirement. The vendor was contacted early about this disclosure but did not respond in any way.
vLLM Mooncake connector through 0.29.0 fails to properly manage GPU KV cache block ownership when concurrent child requests share a single transfer ID in prefill/decode disaggregated deployments. Attackers can trigger GPU memory exhaustion by submitting completion requests with multiple prompts, causing orphaned KV cache blocks to accumulate until process restart and eventually preventing legitimate requests from executing.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1978-L1989
- https://github.com/vllm-project/vllm/pull/49796
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-gpu-kv-cache-leak-via-mooncake-transfer-id-collision
vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints, allowing attackers to allocate unbounded memory. Attackers can supply arbitrary tp_size values in prefill/decode disaggregated deployments to exhaust memory and trigger kernel OOM-kill of the decode worker process.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/utils.py#L569-L573
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/metadata.py#L277
- https://github.com/vllm-project/vllm/pull/51137
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-unvalidated-nixl-tp-size
vLLM through 0.29.0 contains a resource exhaustion vulnerability in MooncakeConnector where rejected prefill requests create ownerless transfer placeholders that are never reclaimed. Attackers can send rejected requests to exhaust sender task pools, causing valid requests to be delayed by up to 480 seconds while health checks continue returning success.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1234-L1242
- https://github.com/vllm-project/vllm/pull/51236
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-resource-exhaustion-via-ownerless-mooncake-transfer-placeholders