Comparison Overview
Ticketmaster Australia
Ticketmaster Australia
None, None, Melbourne, VIC, AU, 3000
Last Update: 07/01/2026
Ticketmaster gives millions of fans fair and easy access to the biggest and best in live entertainment. Driven by innovation, unparalleled scalability, and unmatched support, we are the definitive leader in professional ticketing solutions. Over 12,000 artists, teams, ...
Warner Bros. Discovery
New York City, US
Last Update: 10/09/2026
Warner Bros. Discovery, a premier global media and entertainment company, offers audiences the world’s most differentiated and complete portfolio of content, brands and franchises across television, film, streaming and gaming. The new company combines WarnerMedia’s prem...
Compliance Ranges Comparison
Ticketmaster Australia
Warner Bros. Discovery
Benchmark & Cyber Underwriting Signals
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Ticketmaster Australia in 2026.
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Warner Bros. Discovery in 2026.
Incident History - Ticketmaster Australia (X = Date, Y = Severity)
Ticketmaster Australia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Warner Bros. Discovery (X = Date, Y = Severity)
Warner Bros. Discovery cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ticketmaster Australia
Warner Bros. Discovery
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.