Comparison Overview
Van den Udenhout Groep

Van den Udenhout Groep
Balkweg 1 's-Hertogenbosch, Noord-Brabant 5232 BT, NL
Last Update: 27/10/2025
Uw Audi, Volkswagen, Volkswagen bedrijfswagen, SEAT & ŠKODA dealer in de regio 's-Hertogenbosch, Oss, Son, Eindhoven, Helmond, Veldhoven en Veghel. Volg ons via LinkedIn om op de hoogte te blijven van de ontwikkelingen, evenementen en acties. Bij Van den Udenhout st...

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...
Compliance Ranges Comparison

Van den Udenhout Groep







Freudenberg Group






Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Van den Udenhout Groep in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Freudenberg Group in 2026.
Incident History - Van den Udenhout Groep (X = Date, Y = Severity)
Van den Udenhout Groep cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Freudenberg Group (X = Date, Y = Severity)
Freudenberg Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Van den Udenhout Groep

Freudenberg Group
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