Comparison Overview
GE Hitachi Nuclear Energy
GE Hitachi Nuclear Energy
undefined, Wilmington, North Carolina, 28401, US
Last Update: 25/04/2026
GE Vernova's nuclear business, GE Hitachi, is an alliance created by GE Vernova and Hitachi to serve the global nuclear industry, and is a world-leading provider of advanced reactors, fuel and nuclear services.
Orano
125, Avenue de Paris, Châtillon, 92320, FR
Last Update: 31/03/2026
Opérateur international reconnu dans le domaine des matières nucléaires, Orano apporte des solutions aux défis actuels et futurs, dans l’énergie et la santé. Son expertise ainsi que sa maîtrise des technologies de pointe permettent à Orano de proposer à ses clients des ...
Compliance Ranges Comparison
GE Hitachi Nuclear Energy
Orano
Benchmark & Cyber Underwriting Signals
Incidents vs Nuclear Electric Power Generation Industry Avg (This Year)
No incidents recorded for GE Hitachi Nuclear Energy in 2026.
Incidents vs Nuclear Electric Power Generation Industry Avg (This Year)
No incidents recorded for Orano in 2026.
Incident History - GE Hitachi Nuclear Energy (X = Date, Y = Severity)
GE Hitachi Nuclear Energy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Orano (X = Date, Y = Severity)
Orano cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
GE Hitachi Nuclear Energy
Orano
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: *.*.