Comparison Overview
Nippon Gases Netherlands

Nippon Gases Netherlands
Beugsloepweg 3, Vlaardingen, undefined, 3133 KV, NL
Last Update: 09/03/2026
Gas. Although you don't always realize it, every second of every single day you are in contact with it. Nippon Gases is able to use something as fundamental as air in ways that make factories cleaner and more productive, food taste better, breathing easier and productio...

Brenntag
Messeallee 11, Essen , 45131, DE
Last Update: 16/09/2026
Brenntag is the global market leader in chemicals and ingredients distribution and holds a central role in connecting customers and suppliers of the chemical industry. Headquartered in Essen, Germany, we have more than 18,100 employees worldwide and operate a network of...
Compliance Ranges Comparison

Nippon Gases Netherlands







Brenntag






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

Nippon Gases Netherlands

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