Comparison Overview
Saint-Gobain Finland

Saint-Gobain Finland
Strömberginkuja 2, Helsinki, undefined, 00380, FI
Last Update: 01/04/2026
Autamme rakentamaan erinomaisia elinympäristöjä ja parantamaan ihmisten elämänlaatua. Yhdistämme mukavuuden ja vastuullisuuden parantaaksemme ihmisten hyvinvointia tänään ja tulevaisuudessa. Tule mukaan rakentamaan tulevaisuutta kanssamme! Saint-Gobain designs, manufa...

Builders FirstSource
6031 Connection Dr, Suite 400, Irving, TX, US, 75039
Last Update: 30/03/2026
Builders FirstSource is the nation’s largest supplier of structural building products, value-added components and services to the professional market for new residential construction and repair and remodeling. Our focus is on providing unparalleled service to both large...
Compliance Ranges Comparison

Saint-Gobain Finland







Builders FirstSource






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

Saint-Gobain Finland

Builders FirstSource
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.