Comparison Overview
Ofgem

Ofgem
10 South Colonnade, London, England, E14 4, GB
Last Update: 18/01/2026
Ofgem is Britain’s independent energy regulator. Our role is to protect consumers now and in the future by working to deliver a greener, fairer energy system. Community guidelines: https://www.ofgem.gov.uk/ofgem-privacy-policy Please note our comment and moderation pol...

Enel Group
Viale Regina Margherita 125, Rome, 00198, IT
Last Update: 03/09/2026
We are a multinational company changing the face of energy, one of the world’s leading integrated utilities. As the largest private player in producing clean energy with renewable sources we have more than 92 GW of total capacity, including around 67 GW of renewables. ...
Compliance Ranges Comparison

Ofgem







Enel Group






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

Ofgem

Enel Group
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.