Comparison Overview
Ipsos
Ipsos
35 Rue du Val de Marne, Paris, 75013, FR
Last Update: 08/09/2026
In our world of rapid change, the need for reliable information to make confident decisions has never been greater. At Ipsos we believe our clients need more than a data supplier, they need a partner who can produce accurate and relevant information and turn it into ac...
Kantar
6 More London Place, London, undefined, undefined, GB
Last Update: 09/09/2026
Kantar is the world’s leading marketing data and analytics company. . We have a complete, unique and rounded understanding of how people think, feel and act; globally and locally in over 90 markets. By combining the deep expertise of our people, our data resources and b...
Compliance Ranges Comparison
Ipsos
Kantar
Benchmark & Cyber Underwriting Signals
Incidents vs Market Research Industry Avg (This Year)
No incidents recorded for Ipsos in 2026.
Incidents vs Market Research Industry Avg (This Year)
No incidents recorded for Kantar in 2026.
Incident History - Ipsos (X = Date, Y = Severity)
Ipsos cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kantar (X = Date, Y = Severity)
Kantar cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ipsos
Kantar
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.