Comparison Overview
Saint-Gobain GCC

Saint-Gobain GCC
N/A
Last Update: 02/12/2025
We design, manufacture and distribute materials and solutions that have a positive impact on everyone's life and provide well-being, quality of life and performance, while caring for the planet.

Carrier
13995 Pasteur Blvd, Palm Beach Gardens, 33418, US
Last Update: 01/04/2026
Carrier is a global leader in intelligent climate and energy solutions, pioneering sustainable innovations in climate technologies. Founded by Willis Carrier, the inventor of modern air conditioning, we have been shaping industries and enhancing lives for more than a ce...
Compliance Ranges Comparison

Saint-Gobain GCC







Carrier






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

Saint-Gobain GCC

Carrier
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.