Comparison Overview
Freudenberg Group
Freudenberg Group
Höhnerweg 2-4, Weinheim, 69469, DE
Last Update: 12/09/2026
Freudenberg is a global technology group that strengthens its customers and society long-term through forward-looking innovations. Together with its partners, customers and research institutions, the Freudenberg Group develops leading-edge technologies and excellent pro...
Mercedes-Benz USA
303 Perimeter Center North, Atlanta, 30346, US
Last Update: 21/09/2026
Mercedes-Benz USA, LLC (MBUSA), a Daimler Company, is responsible for the Distribution and Marketing of Mercedes-Benz and smart products in the United States. MBUSA was founded in 1965 and prior to that Mercedes-Benz cars were sold in the United States by Mercedes-Benz...
Compliance Ranges Comparison
Freudenberg Group
Mercedes-Benz USA
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Freudenberg Group in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
Mercedes-Benz USA has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Freudenberg Group (X = Date, Y = Severity)
Freudenberg Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mercedes-Benz USA (X = Date, Y = Severity)
Mercedes-Benz USA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Freudenberg Group
Mercedes-Benz USA
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