Comparison Overview
SEPHORA

SEPHORA
Neuilly sur Seine, 92576 , FR
Last Update: 08/09/2026
Sephora is the world’s leading global prestige beauty retail brand. With our curation of more than 500 brands and our own label, Sephora Collection, we offer the most unique and diverse range of prestige beauty products, tailored to our customers’ needs from fragrance t...

NAPA Auto Parts
2999 Wildwood Pkwy, Atlanta, Georgia, US, 30339
Last Update: 14/09/2026
Through nearly 6,000 auto parts stores and over 16,000 auto care and collision centers in the U.S., NAPA has America’s largest network of parts and care. The NAPA Network is supported by nationwide distribution centers with approximately 800,000 available parts, accesso...
Compliance Ranges Comparison

SEPHORA







NAPA Auto Parts






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
SEPHORA has 2.04% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for NAPA Auto Parts in 2026.
Incident History - SEPHORA (X = Date, Y = Severity)
SEPHORA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NAPA Auto Parts (X = Date, Y = Severity)
NAPA Auto Parts cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

SEPHORA

NAPA Auto Parts
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.