Comparison Overview
Clinique

Clinique
767 Fifth Avenue, New York, NY, US, 10153
Last Update: 04/04/2026
Clinique believes great skin can be created. Because whatever the skin concern, Clinique has safe, clinical solutions. Informed by decades of experience, working with dermatologists, scientists and ophthalmologists. Formulated with the perfect balance of ingredients fo...

O Boticário
Av. Rui Barbosa, 4.110, Parque das Fontes,, São José dos Pinhais, 83.050-010, BR
Last Update: 15/09/2026
A beleza transforma, encanta, conquista e também pode ser conquistada. Eis o ideal de beleza que O Boticário multiplica com seus produtos, lojas e em sua relação com o público. Desde 1977, O Boticário soma inspiração, ousadia, inovação e qualidade, despertando o respei...
Compliance Ranges Comparison

Clinique







O Boticário






Benchmark & Cyber Underwriting Signals
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Clinique in 2026.
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for O Boticário in 2026.
Incident History - Clinique (X = Date, Y = Severity)
Clinique cyber incidents detection timeline including parent company and subsidiaries.
Incident History - O Boticário (X = Date, Y = Severity)
O Boticário cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Clinique

O Boticário
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.