Comparison Overview
Clarus Corporation (CLAR)
Clarus Corporation (CLAR)
2084 E 3900 S, None, Salt Lake City, Utah, US, 84124
Last Update: 02/04/2026
Our mission is to identify, acquire and grow outdoor “super fan” brands through our unique “innovate and accelerate” strategy. Clarus Corporation is a leading designer, developer, manufacturer and distributor of outdoor equipment and lifestyle products focused on the c...
Reckitt
103-105 Bath Road, Slough, Berkshire, GB, SL1 3UH
Last Update: 13/09/2026
Every day, in everything we do, our purpose is to protect, heal and nurture in the relentless pursuit of a cleaner, healthier world. And we have a fight on our hands. A fight to make access to the highest quality hygiene, wellness and nourishment a right and not a privi...
Compliance Ranges Comparison
Clarus Corporation (CLAR)
Reckitt
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Clarus Corporation (CLAR) in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Reckitt in 2026.
Incident History - Clarus Corporation (CLAR) (X = Date, Y = Severity)
Clarus Corporation (CLAR) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Reckitt (X = Date, Y = Severity)
Reckitt cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Clarus Corporation (CLAR)
Reckitt
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.