Comparison Overview
Essilor Group

Essilor Group
147 rue de Paris, None, Charenton le Pont Cedex, None, FR, 94220
Last Update: 14/03/2026
The world's leading ophthalmic optics company, Essilor designs, manufactures and markets a wide range of lenses to improve and protect eyesight. Its mission is to improve lives by improving sight. To support this mission, Essilor allocates more than €200 million to rese...

Olympus Corporation
Nishi-shinjuku 2-3-1 Shinjuku Monolith, Shinjuku-ku, JP
Last Update: 13/09/2026
Olympus is passionate about creating customer-driven solutions for the medical industry. For more than 100 years, Olympus has focused on making people’s lives healthier, safer and more fulfilling by helping detect, prevent, and treat disease, furthering scientific resea...
Compliance Ranges Comparison

Essilor Group







Olympus Corporation






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

Essilor Group

Olympus Corporation
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.