Comparison Overview
WPP Media MENA
WPP Media MENA
43rd Floor, Tower B, Business Central Towers, Dubai , 450383, AE
Last Update: 20/03/2026
Media is changing. So are we. We are WPP's global media collective, built for the AI era. We bring the best platform, people, and partners together to create innovative solutions that deliver unparalleled growth for brands - in every market, every day. Being AI-...
Havas
29/30 Quai de Dion Bouton, Puteaux, FR, 92800
Last Update: 14/09/2026
Founded in 1835 in Paris, Havas is one of the world’s largest global communications groups, with nearly 23,000 people in over 100 countries. With the ambition to help brands unlock Growth, Powered by Desire, Havas brings together creativity, media, technology and produc...
Compliance Ranges Comparison
WPP Media MENA
Havas
Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for WPP Media MENA in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Havas in 2026.
Incident History - WPP Media MENA (X = Date, Y = Severity)
WPP Media MENA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Havas (X = Date, Y = Severity)
Havas cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
WPP Media MENA
Havas
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.