Comparison Overview
Knauf BV

Knauf BV
Mesonweg 8-12, Utrecht, 3542 AL, NL
Last Update: 05/04/2026
At Knauf, we work to strengthen the construction industry with surprising solutions that make our customers more successful. As a family-owned company, we are not only entrepreneurial, but also committed to our customers and our employees. To ensure that all our daily a...

Knauf
Am Bahnhof 7, Iphofen, D-97346, DE
Last Update: 01/04/2026
Everyone sees opportunity differently. Knauf sees opportunity in everyone. Similar to other global businesses, our 41,500 team members in 90 countries across 300 sites provide a huge opportunity for anyone with ambition and energy. Unlike other global businesses, you ...
Compliance Ranges Comparison

Knauf BV







Knauf






Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Knauf BV in 2026.
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Knauf in 2026.
Incident History - Knauf BV (X = Date, Y = Severity)
Knauf BV cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Knauf (X = Date, Y = Severity)
Knauf cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Knauf BV

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