Comparison Overview
GOLD FIELDS

GOLD FIELDS
150 Helen Road, Sandton, Johannesburg, 2196, ZA
Last Update: 30/03/2026
Gold Fields is a globally diversified gold producer with nine mines in Australia, Chile, Ghana, Perú and South Africa, and one project in Canada. We aim to create positive and sustainable value for our employees, communities, capital providers, governments and business...

JSW Steel
Bandra Kurla Complex,, Mumbai, Maharashtra, IN, 400 051
Last Update: 02/04/2026
Over the last 35 years, we have partnered the country in its journey to self-reliance, by embracing sustainability, adopting cutting-edge technology and having innovation and R&D initiatives at the heart of our culture. From humble beginnings with a single plant in 1982...
Compliance Ranges Comparison

GOLD FIELDS







JSW Steel






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

GOLD FIELDS

JSW Steel
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.