Comparison Overview
YTL Power International
YTL Power International
Menara YTL, 205 Jalan Bukit Bintang, Bukit Bintang, 55100, MY
Last Update: 04/12/2025
YTL Power International Berhad [199601034332 (4066684-H)] is an international multi-utility owner and operator, active across key segments of the utilities industry, with operations, investments and projects under development in Malaysia, Singapore, the United Kingdom, ...
Entergy
639 Loyola Ave, New Orleans, 70113, US
Last Update: 04/09/2026
At Entergy (NYSE: ETR), we power life. More than 100 years ago, our founder Harvey Couch started this company with a handshake, some sawdust and a vision. Couch wanted to bring safe, affordable, reliable energy to the Middle South – energy that would power the lives of ...
Compliance Ranges Comparison
YTL Power International
Entergy
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for YTL Power International in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Entergy in 2026.
Incident History - YTL Power International (X = Date, Y = Severity)
YTL Power International cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Entergy (X = Date, Y = Severity)
Entergy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
YTL Power International
Entergy
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.