Comparison Overview
Alenco Inc
Alenco Inc
16201 w 110th St, None, Lenexa, KS, US, 66219
Last Update: 03/04/2026
Alenco’s storied history began way back in 1986 out of Olathe, KS. Our mindset from the beginning was to deliver the finest in Kansas City home improvement and beyond with our quality services. Since our inception, we have rapidly grown up to our present location in Len...
Masco Corporation
17450 College Parkway, Livonia, 48152, US
Last Update: 01/04/2026
Masco Corporation is a global leader in the design, manufacture and distribution of branded home improvement and building products. Our products enhance the way consumers all over the world experience and enjoy their living spaces. Our portfolio of industry-leading bran...
Compliance Ranges Comparison
Alenco Inc
Masco Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Alenco Inc in 2026.
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Masco Corporation in 2026.
Incident History - Alenco Inc (X = Date, Y = Severity)
Alenco Inc cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Masco Corporation (X = Date, Y = Severity)
Masco Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Alenco Inc
Masco Corporation
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: *.*.