Comparison Overview
Harsh & Heavy Industrial
Harsh & Heavy Industrial
40 Waterview Dr, Shelton, 06484, US
Last Update: 27/02/2026
Hubbell’s Harsh & Heavy Industrial sector combines dedicated, market leading brands within the Hubbell portfolio to provide a complete package for companies operating in heavy industry environments. Harsh & Industrial manufactures industrial safety products, power quali...
TE Connectivity
Galway, IE
Last Update: 03/04/2026
TE Connectivity plc (NYSE: TEL) is a global industrial technology leader creating a safer, sustainable, productive and connected future. As a trusted innovation partner, our broad range of connectivity and sensor solutions enable the distribution of power, signal and da...
Compliance Ranges Comparison
Harsh & Heavy Industrial
TE Connectivity
Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Harsh & Heavy Industrial in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for TE Connectivity in 2026.
Incident History - Harsh & Heavy Industrial (X = Date, Y = Severity)
Harsh & Heavy Industrial cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TE Connectivity (X = Date, Y = Severity)
TE Connectivity cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Harsh & Heavy Industrial
TE Connectivity
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: *.*.