Comparison Overview
American Electric Power
American Electric Power
1 Riverside Plaza, Columbus, 43215, US
Last Update: 10/09/2026
Our team at American Electric Power is committed to improving our customers' lives with reliable, affordable power. We are investing $72 billion from 2025 through 2029 to enhance service for customers and support the growing energy needs of our communities. Our more tha...
EDP
Av. 24 de Julho, Lisboa, 1249 - 300, PT
Last Update: 13/09/2026
Our story began 50 years ago. Today, we are a global energy company leading the transition to a more sustainable future. We produce and deliver electricity to millions of families, businesses and communities worldwide, with a strong focus on renewable energy. More than...
Compliance Ranges Comparison
American Electric Power
EDP
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for American Electric Power in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for EDP in 2026.
Incident History - American Electric Power (X = Date, Y = Severity)
American Electric Power cyber incidents detection timeline including parent company and subsidiaries.
Incident History - EDP (X = Date, Y = Severity)
EDP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
American Electric Power
EDP
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.