Comparison Overview
FUJIFILM Corporation

FUJIFILM Corporation
7-3, Akasaka 9-chome, None, Minato-ku, Tokyo, JP, 107-0052
Last Update: 24/03/2026
At Fujifilm we create innovative products and deliver effective solutions in a wide variety of fields to serve society, contribute to the quality of life, and enhance environmental sustainability. Beginning in 1934 as Japan's pioneering photographic film maker, Fujifil...

LyondellBasell
LyondellBasell Tower, Ste. 700, 1221 McKinney Street, Houston, TX, US, 77010
Last Update: 07/10/2026
We are LyondellBasell (NYSE: LYB) – a leader in the global chemical industry creating solutions for everyday sustainable living. Through advanced technology and focused investments, we are enabling a circular and low carbon economy. Across all we do, we aim to unlock va...
Compliance Ranges Comparison

FUJIFILM Corporation







LyondellBasell






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

FUJIFILM Corporation

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