Comparison Overview
CleanLease

CleanLease
Hoogewaard 191, Koudekerk aan den Rijn, 2396 AR, NL
Last Update: 16/02/2026
Al meer dan 100 jaar zijn wij gespecialiseerd in het reinigen en verhuren van hoge kwaliteit textiel. Onze eerste wasserij startte in 1910 in Wormerveer en sinds die tijd zijn we uitgegroeid tot een toonaangevende dienstverlener voor de segmenten ziekenhuizen, zorg en h...

Mohawk Industries
160 S Industrial Blvd, Calhoun, Georgia, US, 30701
Last Update: 30/03/2026
Are you looking for more? At Mohawk Industries, we’re committed to more – more customer solutions, more process improvements, more sustainable manufacturing and more opportunities for our team. As a Fortune 500 global flooring leader with some of the best-known brands i...
Compliance Ranges Comparison

CleanLease







Mohawk Industries






Benchmark & Cyber Underwriting Signals
Incidents vs Textile Manufacturing Industry Avg (This Year)
No incidents recorded for CleanLease in 2026.
Incidents vs Textile Manufacturing Industry Avg (This Year)
No incidents recorded for Mohawk Industries in 2026.
Incident History - CleanLease (X = Date, Y = Severity)
CleanLease cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mohawk Industries (X = Date, Y = Severity)
Mohawk Industries cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CleanLease

Mohawk Industries
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.