Comparison Overview
Barrick Mining Corporation
Barrick Mining Corporation
Toronto, CA
Last Update: 07/09/2026
Barrick is a leading global mining, exploration and development company. We create real, long-term value for all stakeholders through responsible mining, strong partnerships and a disciplined approach to growth.
Vale
Praia de Botafogo, 186, Salas 501 a 1901 , Rio de Janeiro, Rio de Janeiro, BR, 22250-145
Last Update: 10/09/2026
We are a global mining company producing iron ore, pellets, and nickel, and we are committed to becoming one of the safest, most trustworthy mining company in the world. With a workforce of 120,000 employees, we work every day to transform natural resources into prosper...
Compliance Ranges Comparison
Barrick Mining Corporation
Vale
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Barrick Mining Corporation in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Vale in 2026.
Incident History - Barrick Mining Corporation (X = Date, Y = Severity)
Barrick Mining Corporation cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vale (X = Date, Y = Severity)
Vale cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Barrick Mining Corporation
Vale
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.