Comparison Overview
Norton Abrasives

Norton Abrasives
1 New Bond Street, Worcester, 01606, US
Last Update: 22/12/2025
For 130+ years, Norton products have provided the right choices for grinding, cutting, blending, finishing and polishing solutions for a wide array of markets, materials and applications. The Norton brand delivers affordable innovation with the highest productivity in s...

Alfa Laval
Rudeboksvagen 1, Lund, Skane County, SE, 226 55
Last Update: 23/09/2026
Pioneering positive impact! Our pioneering 140-year-old start-up culture is built on the idea that partnership is the key to solving complex problems and unlocking the full potential of resources. So we collaborate closely with our partners, customers, and thought lead...
Compliance Ranges Comparison

Norton Abrasives







Alfa Laval






Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Norton Abrasives in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Alfa Laval in 2026.
Incident History - Norton Abrasives (X = Date, Y = Severity)
Norton Abrasives cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Alfa Laval (X = Date, Y = Severity)
Alfa Laval cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Norton Abrasives

Alfa Laval
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.