Comparison Overview
IWC Schaffhausen

IWC Schaffhausen
Baumgartenstrasse 15, Schaffhausen, undefined, 8201, CH
Last Update: 27/11/2025
IWC Schaffhausen - Engineering beyond time. A Great Place to Work is where you trust those you work for, where you are proud of what you do and where you enjoy working with others. - Robert Levering, co-founder, Great Place to Work According to the latest employee s...

Louis Vuitton
2 Rue du Pont Neuf, Paris, 75001, FR
Last Update: 05/09/2026
For more than 150 years, men and women at Louis Vuitton have shared the same spirit of excellence and passion, reaffirming their expertise every day, the world over. With us, every career is a journey, filled with excitement and challenge, desire and daring. There is no...
Compliance Ranges Comparison

IWC Schaffhausen







Louis Vuitton






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for IWC Schaffhausen in 2026.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
Louis Vuitton has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - IWC Schaffhausen (X = Date, Y = Severity)
IWC Schaffhausen cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Louis Vuitton (X = Date, Y = Severity)
Louis Vuitton cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

IWC Schaffhausen

Louis Vuitton
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.