Comparison Overview
Pop TV
Pop TV
5510 Lincoln Blvd, Playa Vista, 90094, US
Last Update: 24/04/2026
Pop TV, a ViacomCBS network, is a fully distributed entertainment media brand featuring fun, comedy-leaning programming for the Modern Grownup® – engaged fans, raised on network TV, who came of age in the ‘80s and ‘90s. Pop is TV the way it should be – effortlessly ente...
Cinemark
3900 Dallas Parkway, Plano, 75093, US
Last Update: 13/09/2026
Headquartered in Plano, TX, Cinemark Holdings, Inc. provides premium out-of-home entertainment experiences as one of the largest and most influential theatrical exhibition companies in the world with 495 theatres and 5,620 screens in the U.S. and Latin America as of Jun...
Compliance Ranges Comparison
Pop TV
Cinemark
Benchmark & Cyber Underwriting Signals
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Pop TV in 2026.
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Cinemark in 2026.
Incident History - Pop TV (X = Date, Y = Severity)
Pop TV cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cinemark (X = Date, Y = Severity)
Cinemark cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pop TV
Cinemark
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.