Comparison Overview
Iberdrola Australia
Iberdrola Australia
Level 22, 1 Farrer Place, Sydney, NSW, 2000, AU
Last Update: 01/04/2026
Iberdrola Australia is leading Australia’s transition to a clean energy future. Iberdrola Australia generates and sources renewable energy, increases the value of intermittent renewables by firming, and provides customers with clean, reliable and competitively priced en...
Hydro Québec
75 boul. René-Lévesque Ouest, Montréal, H2S 1A4, CA
Last Update: 08/09/2026
Hydro-Québec produit, transporte et distribue de l'électricité. Elle exploite essentiellement des énergies renouvelables, plus particulièrement l'hydroélectricité. Elle fait aussi de la recherche dans les domaines reliés à l'énergie et s'intéresse activement à l'efficac...
Compliance Ranges Comparison
Iberdrola Australia
Hydro Québec
Benchmark & Cyber Underwriting Signals
Incidents vs Renewable Energy Power Generation Industry Avg (This Year)
No incidents recorded for Iberdrola Australia in 2026.
Incidents vs Renewable Energy Power Generation Industry Avg (This Year)
No incidents recorded for Hydro Québec in 2026.
Incident History - Iberdrola Australia (X = Date, Y = Severity)
Iberdrola Australia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hydro Québec (X = Date, Y = Severity)
Hydro Québec cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Iberdrola Australia
Hydro Québec
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.