Comparison Overview
Butler Bros. Industrial Supply
Butler Bros. Industrial Supply
2001 Lisbon Road, Lewiston, 04240, US
Last Update: 02/04/2026
We provide high quality MROP products, innovative solutions, and extraordinary service at a competitive price. We deliver superior value, continuous improvement and cost savings to our customers daily, while providing a safe, healthy, and challenging work environment fo...
Porsche Holding
Louise-Piëch-Straße 2, Salzburg, AT
Last Update: 31/03/2026
Porsche Holding Salzburg is the largest and most successful automotive distributor in Europe. Our roots are in Salzburg, but we now also operate in 29 countries on three continents. Our core expertise: global automotive distribution. Our business divisions: automotive w...
Compliance Ranges Comparison
Butler Bros. Industrial Supply
Porsche Holding
Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for Butler Bros. Industrial Supply in 2026.
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for Porsche Holding in 2026.
Incident History - Butler Bros. Industrial Supply (X = Date, Y = Severity)
Butler Bros. Industrial Supply cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Porsche Holding (X = Date, Y = Severity)
Porsche Holding cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Butler Bros. Industrial Supply
Porsche Holding
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: *.*.