Comparison Overview
Legends Global
Legends Global
61 Broadway, New York, 10006, US
Last Update: 07/07/2026
Legends Global is the premier partner to the world's greatest live events, venues and brands. We deliver a fully integrated solution of premium services that keeps our partners front-and-center through our white-label approach. Our partners engage us at the earliest st...
Qiddiya | القدية
3889, Al Nakheel, Al Nakheel, Riyadh, 12382-6744 , SA
Last Update: 09/09/2026
Qiddiya Investment Company (QIC), a Public Investment Fund (PIF) company, is shaping one of the most transformative visions of Saudi Arabia’s future. By harnessing the Power of Play, we are unlocking new economic opportunities, elevating quality of life, and contributin...
Compliance Ranges Comparison
Legends Global
Qiddiya | القدية
Benchmark & Cyber Underwriting Signals
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Legends Global in 2026.
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Qiddiya | القدية in 2026.
Incident History - Legends Global (X = Date, Y = Severity)
Legends Global cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Qiddiya | القدية (X = Date, Y = Severity)
Qiddiya | القدية cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Legends Global
Qiddiya | القدية
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.