Comparison Overview
Harris Brushes
Harris Brushes
Stoke Prior, Bromsgrove, Worcestershire B60 4AE, GB
Last Update: 19/06/2026
Since 1928 we've been at the cutting-edge of product design; more than 90 years later and that passion for innovation can be seen in every one of our brushes, rollers and decorating tools.
Kohler Co.
444 Highland Drive, Kohler, Wisconsin, US, 53044
Last Update: 03/04/2026
We’re a community of creators. Status quo busters. Difference makers. For more than 150 years, we’ve built our business on a singular mission—helping people live gracious, healthy, and sustainable lives. Thanks to the passion, craftsmanship, and ingenuity of our ass...
Compliance Ranges Comparison
Harris Brushes
Kohler Co.
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Harris Brushes in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Kohler Co. in 2026.
Incident History - Harris Brushes (X = Date, Y = Severity)
Harris Brushes cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kohler Co. (X = Date, Y = Severity)
Kohler Co. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Harris Brushes
Kohler Co.
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: *.*.