Comparison Overview
Newmont Corporation
Newmont Corporation
6900 E Layton Avenue, Denver, Colorado, 80237, US
Last Update: 07/09/2026
Newmont is the world’s leading gold company and a producer of copper, silver, zinc and lead. The Company’s world-class portfolio of assets, prospects and talent is anchored in favorable mining jurisdictions in North America, South America, Australia and Africa. Newmont ...
OCP Group
2-4, rue Al Abtal, Hay Erraha, 20200, Casablanca, Maroc, Casablanca, 20000, MA
Last Update: 11/09/2026
Headquartered in Morocco, OCP Group is one of the world’s largest custodian and supplier of phosphate-based plant nutrition solutions and associated products for soil health and a leader in applied science and education. Our mission is to provide customized plant nutrit...
Compliance Ranges Comparison
Newmont Corporation
OCP Group
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Newmont Corporation in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for OCP Group in 2026.
Incident History - Newmont Corporation (X = Date, Y = Severity)
Newmont Corporation cyber incidents detection timeline including parent company and subsidiaries.
Incident History - OCP Group (X = Date, Y = Severity)
OCP Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Newmont Corporation
OCP Group
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.