Comparison Overview
Royal Road
Royal Road
32 Hue Street, St. Helier, JE2 3RE, JE
Last Update: 20/01/2026
Royal Road (TSXV: RYR) (RRDMF:OTC US) is a mineral exploration and development company with its head office and technical-operations center located in Jersey, Channel Islands. The Company is listed on the TSX Venture Exchange under the ticker RYR and on the Frankfurt ...
First Quantum Minerals
8th Floor – 543 Granville Street, Canada V6C 1X8, CA
Last Update: 10/09/2026
First Quantum Minerals Ltd. is a global mining company producing copper and nickel, as well as gold and cobalt. Our growing portfolio of operations and projects spans four continents and employs around 20,000 people. We are well-known for our ‘can do’ attitude and spec...
Compliance Ranges Comparison
Royal Road
First Quantum Minerals
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Royal Road in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for First Quantum Minerals in 2026.
Incident History - Royal Road (X = Date, Y = Severity)
Royal Road cyber incidents detection timeline including parent company and subsidiaries.
Incident History - First Quantum Minerals (X = Date, Y = Severity)
First Quantum Minerals cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Royal Road
First Quantum Minerals
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.