Comparison Overview
Essar
Essar
Essar House, 11, Keshavrao Khadye Marg, Mahalaxmi, Mumbai, 400 034, IN
Last Update: 14/09/2026
Essar, with an entrepreneurial track record spanning 50+ years, specialises in investing and developing assets to create value in core sectors such as Energy, Infrastructure, Metals & Mining, and Technology & Retail. With a presence in eight countries, Essar generates r...
Sabanci Holding
Sabancı Center 4.Levent, İstanbul, 34330, TR
Last Update: 15/09/2026
Sabancı Holding is one of Turkey’s leading conglomerate, engaged in a wide variety of business activities through its subsidiaries and affiliates, mainly in the banking, financial services, energy, industrials, building materials and retail sectors. Our Group companies ...
Compliance Ranges Comparison
Essar
Sabanci Holding
Benchmark & Cyber Underwriting Signals
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Essar in 2026.
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Sabanci Holding in 2026.
Incident History - Essar (X = Date, Y = Severity)
Essar cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sabanci Holding (X = Date, Y = Severity)
Sabanci Holding cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Essar
Sabanci Holding
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.