Comparison Overview
Wavemaker Canada
Wavemaker Canada
155 Queens Quay E, Toronto, Ontario, M5A 0W4, CA
Last Update: 28/02/2026
At Wavemaker we believe there is always a better way to grow. We know that growth models of the past will not serve the future. Established approaches and traditional thinking are being explored in every sector, in every market. But exceptional growth requires uncomfort...
Clear Channel Europe
33 Golden Square, London, England, GB, W1F 9
Last Update: 14/09/2026
Clear Channel Europe is a division of leading global Out of Home media company, Clear Channel Outdoor Holdings, Inc. (NYSE: CCO). The Clear Channel Europe portfolio spans 14 markets with 260,000 advertising panels. Clear Channel Europe has 2,600 dedicated employees. O...
Compliance Ranges Comparison
Wavemaker Canada
Clear Channel Europe
Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Wavemaker Canada in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Clear Channel Europe in 2026.
Incident History - Wavemaker Canada (X = Date, Y = Severity)
Wavemaker Canada cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Clear Channel Europe (X = Date, Y = Severity)
Clear Channel Europe cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Wavemaker Canada
Clear Channel Europe
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.