Comparison Overview
Knauf Gesellschaft m.b.H. Österreich

Knauf Gesellschaft m.b.H. Österreich
Knaufstraße 1, Weißenbach bei Liezen, Styria 8940, AT
Last Update: 24/04/2026
Knauf ist der führende Anbieter für die sichere, gesunde und behagliche Gestaltung von Lebensräumen. Die Knauf Gesellschaft m.b.H. in Österreich ist ein Unternehmen der Knauf Gruppe, das auf Systeme für Trockenbau, Spachtelmassen, Putz und Fassade spezialisiert ist. Kna...

Owens Corning
World Headquarters, Toledo, 43659, US
Last Update: 01/04/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

Knauf Gesellschaft m.b.H. Österreich







Owens Corning






Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Knauf Gesellschaft m.b.H. Österreich in 2026.
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Owens Corning in 2026.
Incident History - Knauf Gesellschaft m.b.H. Österreich (X = Date, Y = Severity)
Knauf Gesellschaft m.b.H. Österreich 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

Knauf Gesellschaft m.b.H. Österreich

Owens Corning
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.