Comparison Overview
TATA Power
TATA Power
Tata Power, Bombay House, 24 Homi Mody Street, Mumbai - 400 001, Mumbai, 400009, IN
Last Update: 03/09/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...
E.ON
Brüsseler Platz 1, Essen, 45131, DE
Last Update: 09/09/2026
We are one of Europe's largest energy companies with the business areas of energy networks, energy infrastructure solutions and energy sales. It’s on us to make new energy work, and we are actively leading energy’s future – putting our customers first and delivering inn...
Compliance Ranges Comparison
TATA Power
E.ON
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for TATA Power in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for E.ON in 2026.
Incident History - TATA Power (X = Date, Y = Severity)
TATA Power cyber incidents detection timeline including parent company and subsidiaries.
Incident History - E.ON (X = Date, Y = Severity)
E.ON cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
TATA Power
E.ON
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.