Comparison Overview
Vedanta Group
Vedanta Group
Vedanta Resources, London, GB
Last Update: 08/09/2026
We operate on the belief that our people are our core assets and we consistently endeavour towards developing their potential to be our future leaders and key employees. We currently operate in India, South Africa, Liberia and Namibia, through our various subsidiaries. ...
Future Group India
Tower C, 24/7 Park,, Mumbai, 400083, IN
Last Update: 13/09/2026
About Working with Future Group gives you an opportunity to be part of a family with a unique culture and beliefs. Drawing from the vision of modern Indian retail, we have built a company that our people are proud of and our customers and communities value. Missio...
Compliance Ranges Comparison
Vedanta Group
Future Group India
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
Vedanta Group has 60.0% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Future Group India in 2026.
Incident History - Vedanta Group (X = Date, Y = Severity)
Vedanta Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Future Group India (X = Date, Y = Severity)
Future Group India cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Vedanta Group
Future Group India
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.