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

Schaeffler
Industriestraße 1-3, Herzogenaurach, 91074, DE
Last Update: 14/09/2026
The Schaeffler Group has been driving forward groundbreaking inventions and developments in the field of motion technology for over 75 years. With innovative technologies, products, and services for electric mobility, CO₂-efficient drives, chassis solutions and renewabl...
Compliance Ranges Comparison

Clarus Corporation (CLAR)







Schaeffler






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 Schaeffler 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 - Schaeffler (X = Date, Y = Severity)
Schaeffler cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Clarus Corporation (CLAR)

Schaeffler
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