Comparison Overview
Minera Michilla S. A.

Minera Michilla S. A.
Camino a Tocopilla Kilómetro 110, Mejillones, undefined, undefined, CL
Last Update: 19/04/2026
Minera Michilla S.A., una sociedad anónima cerrada chilena, que tiene por objeto la exploración, extracción, explotación, producción, beneficio y el comercio de minerales de cobre, de cátodos de cobre y de los productos y subproductos que se obtengan y provengan de dich...

Sandvik
Kungsbron 1, Stockholm, 111 22, SE
Last Update: 20/09/2026
Sandvik is a global, high-tech engineering group providing solutions that enhance productivity, profitability and sustainability for the manufacturing, mining and infrastructure industries. We are at the forefront of digitalization and focus on optimizing our customers’...
Compliance Ranges Comparison

Minera Michilla S. A.







Sandvik






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

Minera Michilla S. A.

Sandvik
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.