Comparison Overview
Dove
Dove
London, GB
Last Update: 21/02/2026
Since launching in 1957, Dove has become the world’s leading personal care brand by championing superior care – from iconic products, such as our #1 dermatologist-recommended beauty bar and body wash, to collective action that delivers real impact for every member of o...
Kimberly-Clark
351 Phelps Dr, Irving, TX, US, 75038
Last Update: 14/09/2026
At Kimberly-Clark, everything we do begins with care — for people, for communities, and for the planet we share. For more than 150 years, our brands have created essentials that make life better for billions of people every day. Better Care for a Better World is more th...
Compliance Ranges Comparison
Dove
Kimberly-Clark
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Dove in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Kimberly-Clark in 2026.
Incident History - Dove (X = Date, Y = Severity)
Dove cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kimberly-Clark (X = Date, Y = Severity)
Kimberly-Clark cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Dove
Kimberly-Clark
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.