Comparison Overview
RTL Hrvatska

RTL Hrvatska
Krapinska 45, Zagreb, undefined, 10000, HR
Last Update: 22/12/2025
RTL Hrvatska is owned by CME Media Enterprises B.V. As a commercial television, RTL started broadcasting in Croatia in 2004, while today it has three main national channels (RTL, RTL2 and RTL Kockica), four IPTV channels (RTL Living, RTL Passion, RTL Crime and RTL Adri...

CBC/Radio-Canada
181 Queen Street, Ottawa, K1Y 1E4, CA
Last Update: 12/09/2026
CBC/Radio-Canada is Canada's national public broadcaster and a strong advocate of Canadian culture. We offer a unique space and a fresh Canadian perspective with unmatched cultural, musical and documentary programming. We do it in French, English and eight Aboriginal l...
Compliance Ranges Comparison

RTL Hrvatska







CBC/Radio-Canada






Benchmark & Cyber Underwriting Signals
Incidents vs Broadcast Media Production and Distribution Industry Avg (This Year)
No incidents recorded for RTL Hrvatska in 2026.
Incidents vs Broadcast Media Production and Distribution Industry Avg (This Year)
No incidents recorded for CBC/Radio-Canada in 2026.
Incident History - RTL Hrvatska (X = Date, Y = Severity)
RTL Hrvatska cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CBC/Radio-Canada (X = Date, Y = Severity)
CBC/Radio-Canada cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

RTL Hrvatska

CBC/Radio-Canada
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.