Comparison Overview
NextEnergy Solar Fund (NESF)
NextEnergy Solar Fund (NESF)
1 Royal Plaza, Royal Avenue, St Peter Port, Guernsey, GY1 3PPGY1 2HL, GG
Last Update: 20/12/2025
NextEnergy Solar Fund is a specialist solar energy and energy storage investment company that is listed on the London Stock Exchange as part of the ESCC category and is a FTSE 250 constituent. NextEnergy Solar Fund's investment objective is to provide ordinary share...
Hitachi Energy
Brown-Boveri Strasse 5, Zurich, CH
Last Update: 01/04/2026
Hitachi Energy is a global technology leader in electrification, powering a sustainable energy future with innovative power grid technologies with digital at the core. Over three billion people depend on our technologies to power their daily lives. With over a century i...
Compliance Ranges Comparison
NextEnergy Solar Fund (NESF)
Hitachi Energy
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for NextEnergy Solar Fund (NESF) in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Hitachi Energy in 2026.
Incident History - NextEnergy Solar Fund (NESF) (X = Date, Y = Severity)
NextEnergy Solar Fund (NESF) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hitachi Energy (X = Date, Y = Severity)
Hitachi Energy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NextEnergy Solar Fund (NESF)
Hitachi Energy
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: *.*.