Comparison Overview
AdPeople Worldwide
AdPeople Worldwide
3 Columbus Circle, New York, NY, 10019, US
Last Update: 19/03/2026
AdPeople Worldwide is a global advertising agency network that operates in a digital world. We create brand stories that come to life through customer-centric content, delivered with relevant marketing technology platforms in over 70 markets. Expert employees from...
VML
3 WTC 175 Greenwich Street, New York, New York, US
Last Update: 15/09/2026
VML is a global powerhouse born from the unification of Wunderman Thompson and VMLY&R — two of the world's most powerful and accomplished creative agencies with complementary capabilities and geographic strengths. We have an industry-unique opportunity to provide our cl...
Compliance Ranges Comparison
AdPeople Worldwide
VML
Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for AdPeople Worldwide in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for VML in 2026.
Incident History - AdPeople Worldwide (X = Date, Y = Severity)
AdPeople Worldwide cyber incidents detection timeline including parent company and subsidiaries.
Incident History - VML (X = Date, Y = Severity)
VML cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AdPeople Worldwide
VML
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.