Comparison Overview
DNV Cyber

DNV Cyber
Veritasveien, Oslo, 1363, NO
Last Update: 06/03/2026
DNV Cyber is a leading cybersecurity services provider. We empower businesses with complex needs to become safer and more resilient with tailored solutions. Our global team of more than 500 experts brings over 30 years of IT and industrial control system security experi...

Hatch
2800 Speakman Dr, Mississauga, Ontario, CA, L5K2R7
Last Update: 24/09/2026
Our organization is passionately committed to the pursuit of a better world through positive change. We embrace your visions as our own and partner with you to develop better ideas that are smarter, more efficient, and innovative. Our global network of 10,000 profession...
Compliance Ranges Comparison

DNV Cyber







Hatch






Benchmark & Cyber Underwriting Signals
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for DNV Cyber in 2026.
Incidents vs Professional Services Industry Avg (This Year)
Hatch has 96.08% more incidents than the average of all companies with at least one recorded incident.
Incident History - DNV Cyber (X = Date, Y = Severity)
DNV Cyber cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hatch (X = Date, Y = Severity)
Hatch cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

DNV Cyber

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