Comparison Overview
Carolina Herrera

Carolina Herrera
501 7th Avenue, New York, 10018, US
Last Update: 05/03/2026
Carolina Herrera is a New York-based fashion house recognized for creating beautifully crafted collections synonymous with impeccable style and bold elegance. With the appointment of Wes Gordon as Creative Director in 2018, the House has reinforced its commitment to the...

Tommy Hilfiger
Danzigerkade 165, Amsterdam, North Holland, NL, 1013
Last Update: 12/09/2026
TOMMY HILFIGER is one of the world’s leading designer lifestyle brands creating a platform that inspires the modern American spirit, while committing to wasting nothing and welcoming all. Founded in 1985, Tommy Hilfiger delivers premium styling, quality and value to c...
Compliance Ranges Comparison

Carolina Herrera







Tommy Hilfiger






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Carolina Herrera in 2026.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Tommy Hilfiger in 2026.
Incident History - Carolina Herrera (X = Date, Y = Severity)
Carolina Herrera cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tommy Hilfiger (X = Date, Y = Severity)
Tommy Hilfiger cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Carolina Herrera

Tommy Hilfiger
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.