Comparison Overview
Vedanta | FACOR
Vedanta | FACOR
Bhadrak, 756135, IN
Last Update: 20/04/2026
Ferro Alloys Corporation Limited (FACOR) is one of the oldest and reputed producers of High Carbon Ferro Chrome or Charge Chrome in India, known for its consistent supply, best-in-class quality, and service in the domestic as well as Global Market for four decades. The ...
Tata Steel
Bombay House, 24, Homi Mody Street, Mumbai, 400001, IN
Last Update: 12/09/2026
Tata Steel is one of the world’s most diversified integrated steel producers, with a capacity of 35 million tonnes per annum (MTPA) across India, the Netherlands, the UK, and Thailand. The World Economic Forum has recognised Tata Steel’s Jamshedpur, Kalinganagar and IJm...
Compliance Ranges Comparison
Vedanta | FACOR
Tata Steel
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Vedanta | FACOR in 2026.
Incidents vs Mining Industry Avg (This Year)
Tata Steel has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Vedanta | FACOR (X = Date, Y = Severity)
Vedanta | FACOR cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tata Steel (X = Date, Y = Severity)
Tata Steel cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Vedanta | FACOR
Tata Steel
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.