Comparison Overview
BHP
BHP
171 Collins Street, Melbourne, 3000, AU
Last Update: 07/09/2026
We are supplying the resources the world needs to help build a better, clearer future. Copper for renewable energy. Potash for sustainable farming. Iron ore and metallurgical coal for the steel needed for global infrastructure and the energy transition. #FutureIsClear ...
AngloGold Ashanti
Greenwood Village, Denver, 80111, US
Last Update: 15/09/2026
AngloGold Ashanti plc is a global gold mining company with a diverse, high-quality portfolio of operations, projects and exploration activities across 10 countries on four continents. We pursue value-creating opportunities involving other minerals, where we can leverage...
Compliance Ranges Comparison
BHP
AngloGold Ashanti
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
BHP has 58.33% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for AngloGold Ashanti in 2026.
Incident History - BHP (X = Date, Y = Severity)
BHP cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AngloGold Ashanti (X = Date, Y = Severity)
AngloGold Ashanti cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BHP
AngloGold Ashanti
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.