Comparison Overview
Mindshare Danmark
Mindshare Danmark
Holmbladsgade 133, Copenhagen, Capital Region, 2300, DK
Last Update: 08/03/2026
Hos Mindshare arbejder vi sammen i krydsfeltet mellem medier, kreativitet og data. Vi mener, at det skaber mere sammenhængende løsninger med en højere fleksibilitet og hastighed. Vores arbejde bygger på dokumentation og erfaring. Med dedikerede medarbejdere på tværs af...
dentsu
1-8-1 Higashi-shimbashi, Tokyo, JP
Last Update: 15/09/2026
We are dentsu. We team together to help brands predict and plan for disruptive future opportunities and create new paths to growth in the sustainable economy. We know people better than anyone else and we use those insights to connect brand, content, commerce and experi...
Compliance Ranges Comparison
Mindshare Danmark
dentsu
Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Mindshare Danmark in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for dentsu in 2026.
Incident History - Mindshare Danmark (X = Date, Y = Severity)
Mindshare Danmark cyber incidents detection timeline including parent company and subsidiaries.
Incident History - dentsu (X = Date, Y = Severity)
dentsu cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Mindshare Danmark
dentsu
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.