Comparison Overview
Heidelberg Materials Deutschland
Heidelberg Materials Deutschland
Berliner Straße 6, Heidelberg, Baden-Württemberg, 69120, DE
Last Update: 03/12/2025
Hier gibt es die Neuigkeiten von Deutschlands Marktführer bei Zement sowie führendem Produzenten für Beton und Zuschlagstoffe. Die internationalen News aus über 50 Ländern gibt’s bei @heidelbergmaterials und für diejenigen, die etwas handfestes haben möchten, gibt es u...
Owens Corning
World Headquarters, Toledo, 43659, US
Last Update: 19/09/2026
Owens Corning is a building products leader committed to building a sustainable future through material innovation. Our products provide durable, sustainable, energy-efficient solutions that leverage our unique capabilities and market-leading positions to help our custo...
Compliance Ranges Comparison
Heidelberg Materials Deutschland
Owens Corning
Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Heidelberg Materials Deutschland in 2026.
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Owens Corning in 2026.
Incident History - Heidelberg Materials Deutschland (X = Date, Y = Severity)
Heidelberg Materials Deutschland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Owens Corning (X = Date, Y = Severity)
Owens Corning cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Heidelberg Materials Deutschland
Owens Corning
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