Comparison Overview
Wavemaker Portugal
Wavemaker Portugal
Av. 24 de Julho, Lisbon, Portugal, 1200-869 Lisboa,, PT
Last Update: 09/03/2026
Future Makers: Ligados pela nossa forma de pensar a Consumer Journey, ajudamos os nossos clientes a transformarem os comportamentos do público em insights e em decisões que serão certas hoje, para um próspero amanhã. O nosso trabalho é apoiar, consultar e realizar toda...
Publicis Groupe
133, avenue des Champs-Elysées, Paris, 75008, FR
Last Update: 13/09/2026
Founded in 1926 by Marcel Bleustein-Blanchet, today Publicis Groupe is one of the largest communications groups in the world and a leader in marketing, communication, and digital business transformation, led by Arthur Sadoun, the third CEO in its history. Publicis Gro...
Compliance Ranges Comparison
Wavemaker Portugal
Publicis Groupe
Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Wavemaker Portugal in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Publicis Groupe in 2026.
Incident History - Wavemaker Portugal (X = Date, Y = Severity)
Wavemaker Portugal cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Publicis Groupe (X = Date, Y = Severity)
Publicis Groupe cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Wavemaker Portugal
Publicis Groupe
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.