Comparison Overview
Carhartt
Carhartt
5750 Mercury Drive, Dearborn, US
Last Update: 27/08/2026
Carhartt manufactures premium clothing known for exceptional durability, comfort, quality of construction and fit that you can feel in the fabrics and see in the performance. Established in Detroit in 1889, our corporate headquarters is today located in Dearborn, Mi...
MANGO
Mercaders 9-11, Palau Solità i Plegamans, 08184, ES
Last Update: 09/09/2026
Mango, one of the leading international fashion groups, is a global company with design and creativity at the heart of its business model and a strategy based on constant innovation, the pursuit of sustainability and a complete ecosystem of channels and partners. With ...
Compliance Ranges Comparison
Carhartt
MANGO
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
Carhartt has 57.98% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
MANGO has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Carhartt (X = Date, Y = Severity)
Carhartt cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MANGO (X = Date, Y = Severity)
MANGO cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Carhartt
MANGO
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.