Comparison Overview
Johnson Matthey

Johnson Matthey
5th Floor, 2 Gresham Street, London, EC2V 7AD, GB
Last Update: 04/04/2026
We are Johnson Matthey, a global leader in sustainable technologies. Our customers include many of the world’s leading energy, chemicals and automotive companies. They depend on us to use our cutting-edge science to enable them to decarbonise, reduce harmful emissions ...

dsm-firmenich
N/A
Last Update: 16/09/2026
We are dsm-firmenich – innovators in nutrition, health, and beauty. We bring progress to life by combining the essential, the desirable, and the sustainable. From our master perfumers and flavorists to our expert nutritionists and scientists, our trailblazing teams wo...
Compliance Ranges Comparison

Johnson Matthey







dsm-firmenich






Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Johnson Matthey in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for dsm-firmenich in 2026.
Incident History - Johnson Matthey (X = Date, Y = Severity)
Johnson Matthey cyber incidents detection timeline including parent company and subsidiaries.
Incident History - dsm-firmenich (X = Date, Y = Severity)
dsm-firmenich cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Johnson Matthey

dsm-firmenich
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.