Comparison Overview
E.ON Next
E.ON Next
undefined, London, Leicester & Nottingham, undefined, undefined, GB
Last Update: 19/03/2026
At E.ON Next, we’re determined to make new energy work for everyone. We want to do that by helping remove the barriers of the energy transition, so that our customers can reduce both their bills and their environmental impact, by saving CO2. We’re E.ON Next. Join our UK...
TATA Power
Tata Power, Bombay House, 24 Homi Mody Street, Mumbai - 400 001, Mumbai, 400009, IN
Last Update: 01/04/2026
Tata Power is one of India’s largest integrated power companies and together with its subsidiaries and jointly controlled entities, has an installed/managed capacity of 14,294 MW. The Company has a presence across the entire power value chain - generation of renewable a...
Compliance Ranges Comparison
E.ON Next
TATA Power
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for E.ON Next in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for TATA Power in 2026.
Incident History - E.ON Next (X = Date, Y = Severity)
E.ON Next cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TATA Power (X = Date, Y = Severity)
TATA Power cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
E.ON Next
TATA Power
FAQ
Latest Global CVEs
Capgo (Cap-go/capgo) before 12.128.2 contains an improper access control vulnerability in the SECURITY DEFINER PostgREST RPC function public.record_build_time, which is granted to the anon role and callable with only the public Supabase publishable (sb_publishable_*) anon key. An unauthenticated attacker can insert rows into public.build_logs for arbitrary organizations and, because the function uses ON CONFLICT (build_id, org_id) DO UPDATE, can overwrite existing usage/billing records by reusing the same build_id for a target org. This enables cross-tenant tampering of billing build logs and financial-impact denial of service by inflating billable build time.
Cap-go before 12.128.2 contains an authentication logic flaw that lets an attacker register and control an account bound to a victim's email address before that email is verified. By enabling two-factor authentication on the pre-registered account, the attacker gains control over the account claimed under the victim's identity, allowing them to read and modify its state and enforce organization-level policies, while the legitimate user is denied access to the account tied to their own email.
Capgo before 12.128.2 contains a flaw in the Enforce Password Policy feature: after a Super Admin enables the policy and successfully changes their password to a compliant one, the backend does not update the password-compliance state. As a result, the backend continues to treat the account as non-compliant and repeatedly forces password-reset prompts, permanently locking the Super Admin out of organization access (organization lockout / denial of service) despite valid authentication.
Capgo before 12.128.2 contains a cross-tenant authorization bypass vulnerability in PostgREST endpoints that allows org-scoped read API keys to access other tenants' webhook secrets and delivery logs. Attackers can query the webhooks and webhook_deliveries endpoints to exfiltrate HMAC signing secrets and delivery payloads, enabling forged webhook events against victim organizations.
Cap-go before 12.128.2 contains an authentication bypass vulnerability in OTP verification that allows attackers to bypass email verification by modifying server responses. Attackers can intercept OTP verification requests and manipulate HTTP responses to falsely mark verification successful, enabling unauthorized 2FA enablement and account takeover.