Comparison Overview
Rodan + Fields
Rodan + Fields
60 Spear Street, San Francisco, CA, US, 94105
Last Update: 13/09/2026
We are Rodan + Fields, founded by Stanford-trained dermatologists with a mission to revolutionize skincare for women everywhere. Our products are dermatologist-developed and inspired by Women-Backed Science™, delivering real, visible results. We understand what works f...
Unilever
100 Victoria Embankment, Blackfriars, London, GB, EC4Y 0DY
Last Update: 11/09/2026
Every day, 3.4 billion people around the world enjoy our products - from ground-breaking brands like Hellmann's, Domestos, Dove and Rexona (to name just a few). Our brands lead the way - innovating in their fields, delighting their consumers and powering our business fo...
Compliance Ranges Comparison
Rodan + Fields
Unilever
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Rodan + Fields in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Unilever in 2026.
Incident History - Rodan + Fields (X = Date, Y = Severity)
Rodan + Fields cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Unilever (X = Date, Y = Severity)
Unilever cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Rodan + Fields
Unilever
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.