Comparison Overview
EDP España

EDP España
undefined, Madrid, Comunidad de Madrid, 28033, ES
Last Update: 16/01/2026
Estamos creado una nueva energía en el planeta. Lideramos la transición energética con la ambición de ser 100% verdes en 2030 Somos una compañía global, presente en 30 mercados, pero con más de 100 años de historia en España donde estamos presentes en la generación, dis...

Saudi Electricity Company
Riyadh, SA
Last Update: 01/04/2026
The Saudi Electricity Company was established on the 5th of April in the year 2000, incorporated in accordance with Council of Ministers Mandate No. 169 dated November 30th, 1998, the Saudi Electricity Company was born out of the merger of smaller regional power company...
Compliance Ranges Comparison

EDP España







Saudi Electricity Company






Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for EDP España in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Saudi Electricity Company in 2026.
Incident History - EDP España (X = Date, Y = Severity)
EDP España cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Saudi Electricity Company (X = Date, Y = Severity)
Saudi Electricity Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

EDP España

Saudi Electricity Company
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.