Comparison Overview
EDP Energia Polska
EDP Energia Polska
ul. Aleje Jerozolimskie, Warsaw, undefined, 00-807, PL
Last Update: 08/01/2026
Grupa EDP jest światową firmą energetyczną działającą we wszystkich obszarach łańcucha przemysłu energetycznego od wytwarzania, poprzez dystrybucję i dostarczanie gazu i elektryczności, obecną na 4 kontynentach w 20 państwach. EDP Energia Polska, firma zajmująca się sp...
Xcel Energy
401 Nicollet Mall, Minneapolis, US
Last Update: 01/04/2026
A leading energy provider, dedicated to excellence. We make energy work better for our customers, helping them thrive every day. That means always raising the bar - delivering better service and providing more reliable, resilient and sustainable energy to the eight stat...
Compliance Ranges Comparison
EDP Energia Polska
Xcel Energy
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for EDP Energia Polska in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Xcel Energy in 2026.
Incident History - EDP Energia Polska (X = Date, Y = Severity)
EDP Energia Polska cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Xcel Energy (X = Date, Y = Severity)
Xcel Energy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
EDP Energia Polska
Xcel 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: *.*.