Comparison Overview
The Weir Group PLC
The Weir Group PLC
1 West Regent Street, Glasgow, G2 1RW, GB
Last Update: 29/03/2026
Weir is a global leader in mining technology. We recognise that our planet’s future depends on the transition to renewable energy, and that transition can only happen with the metals and minerals our mining customers deliver. We combine our deep customer insights, worl...
Orica
1 Nicholson St, East Melbourne, 3000, AU
Last Update: 12/09/2026
Our story began in 1874, when we first supplied explosives to the Victorian goldfields in Australia. Since then, we have grown to become one of the world’s leading mining and infrastructure solutions providers. From the production and supply of explosives, blasting s...
Compliance Ranges Comparison
The Weir Group PLC
Orica
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for The Weir Group PLC in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Orica in 2026.
Incident History - The Weir Group PLC (X = Date, Y = Severity)
The Weir Group PLC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Orica (X = Date, Y = Severity)
Orica cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
The Weir Group PLC
Orica
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.