Comparison Overview
ESAB
ESAB
909 Rose Ave, North Bethesda, Maryland, 20852, US
Last Update: 28/02/2026
ESAB is a world leader in the production of welding consumables and equipment. Our brand is synonymous with world-leading expertise in the following key areas: * Manual welding and cutting equipment * Welding consumables * Welding automation * Cut...
Nippon Steel Corporation
2-6-1 Marunouchi, Chiyoda-ku, Tokyo 100-8071, Japan, Tokyo, 2-6-1 Marunouchi, Chiyoda-ku, Tokyo 100-8071, Japan, JP, 〒100-8071
Last Update: 07/07/2026
＜Nippon Steel Corporation does not recognize this account as OFFICIAL, but it is open for LinkedIn subscribers.＞ On April 1, 2019, we renamed ourselves as “Nippon Steel Corporation” (from Nippon Steel and Sumitomo Metal Corporation), to keep in pace with our advance as...
Compliance Ranges Comparison
ESAB
Nippon Steel Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for ESAB in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Nippon Steel Corporation in 2026.
Incident History - ESAB (X = Date, Y = Severity)
ESAB cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Nippon Steel Corporation (X = Date, Y = Severity)
Nippon Steel Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ESAB
Nippon Steel 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: *.*.