Comparison Overview
Elia Group

Elia Group
Boulevard de l'Empereur 20, Brussels, 1000, BE
Last Update: 16/04/2026
Elia Group is a key player in electricity transmission. We ensure that production and consumption are balanced around the clock, supplying 30 million end users with electricity. Through our subsidiaries in Belgium (Elia) and the north and east of Germany (50Hertz), we o...

Neoenergia
Praia do Flamengo, 78, Rio de Janeiro, Rio de Janeiro, BR
Last Update: 01/04/2026
Somos uma companhia de capital aberto com ações (NEOE3) negociadas na Bolsa de Valores de São Paulo. Parte do grupo espanhol Iberdrola, atuamos no Brasil desde 1997, e atualmente, somos uma das líderes do setor elétrico do país. Estamos presentes em 18 estados e no Dist...
Compliance Ranges Comparison

Elia Group







Neoenergia






Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Elia Group in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Neoenergia in 2026.
Incident History - Elia Group (X = Date, Y = Severity)
Elia Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Neoenergia (X = Date, Y = Severity)
Neoenergia cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Elia Group

Neoenergia
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.