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...
Levi Strauss & Co.
1155 Battery St, San Francisco, US
Last Update: 05/09/2026
You’re an original. So are we. We’re a company of people who like to forge our own path. We invented the blue jean in 1873, and we reinvented khaki pants in 1986. We pioneered labor and environmental guidelines in manufacturing. And we work to build sustainability int...
Compliance Ranges Comparison
Carhartt
Levi Strauss & Co.
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)
Levi Strauss & Co. has 1.96% 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 - Levi Strauss & Co. (X = Date, Y = Severity)
Levi Strauss & Co. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Carhartt
Levi Strauss & Co.
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout