Comparison Overview
Jundu

Jundu
Rodovia SP 215 Km 116, Descalvado, São Paulo, 13690-000, BR
Last Update: 05/11/2025
Na Jundu, somos uma família de profissionais dedicados, mais de 300 forças unificadas por um propósito que nos impulsiona: transformar de maneira responsável recursos minerais em soluções geradoras de riqueza para a sociedade. Com Ciência e Inovação somos guiados por pr...

Maaden
Saudi Arabia, Riyadh, SA, 11537
Last Update: 10/06/2026
Maaden is Saudi Arabia’s engine of industrial transformation and one of the world’s top ten mining giants by market cap and fastest growing globally. We’re building the future of mining, creating fully integrated value chains across gold, phosphate, bauxite, copper and ...
Compliance Ranges Comparison

Jundu







Maaden






Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Jundu in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Maaden in 2026.
Incident History - Jundu (X = Date, Y = Severity)
Jundu cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Maaden (X = Date, Y = Severity)
Maaden cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Jundu

Maaden
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.