Comparison Overview
Harmony Gold Mining Company Limited

Harmony Gold Mining Company Limited
Randfontein Office Park, Randfontein , 9460, ZA
Last Update: 04/04/2026
Harmony Gold Mining Company Limited (Harmony), a world-class gold mining and exploration company, has operations and assets in South Africa and Papua New Guinea (PNG). Harmony has more than 70 years’ experience in the industry. Company assets include one open pit mine a...

JSW Steel
Bandra Kurla Complex,, Mumbai, Maharashtra, IN, 400 051
Last Update: 10/09/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

Harmony Gold Mining Company Limited







JSW Steel






Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Harmony Gold Mining Company Limited in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for JSW Steel in 2026.
Incident History - Harmony Gold Mining Company Limited (X = Date, Y = Severity)
Harmony Gold Mining Company Limited 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

Harmony Gold Mining Company Limited

JSW Steel
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.