Comparison Overview
Clé de Peau Beauté

Clé de Peau Beauté
390 Madison Avenue, New York, New York, 10017, US
Last Update: 10/12/2025
Clé de Peau Beauté, the premier luxury skincare and makeup brand from Shiseido Cosmetics, was founded in 1982 as the ultimate expression of elegance and science. Forever guided by an exquisite aesthetic sensibility and intelligence, Clé de Peau Beauté has instilled its ...

Mary Kay Global
16251 Dallas Parkway, Addison, US
Last Update: 15/09/2026
About Mary Kay - Then. Now. Always. One of the original glass ceiling breakers, Mary Kay Ash founded her dream beauty brand in Texas in 1963 with one goal: to enrich women’s lives. That dream has blossomed into a global company with unlimited opportunities to do somethi...
Compliance Ranges Comparison

Clé de Peau Beauté







Mary Kay Global






Benchmark & Cyber Underwriting Signals
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Clé de Peau Beauté in 2026.
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Mary Kay Global in 2026.
Incident History - Clé de Peau Beauté (X = Date, Y = Severity)
Clé de Peau Beauté cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mary Kay Global (X = Date, Y = Severity)
Mary Kay Global cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Clé de Peau Beauté

Mary Kay Global
FAQ
Latest Global CVEs
A security flaw has been discovered in THU-MIG yoloe up to 40cd606cabdbe2b566d6f14a6b162c89206e9a1b. This affects the function eval of the file ultralytics/nn/autobackend.py of the component AutoBackend Model Loading. The manipulation of the argument imgsz/names/kpt_shape results in improper neutralization of directives in dynamically evaluated code. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.
Coder before 2.34.7 contains an IP spoofing vulnerability in the ExtractRealIPAddress middleware that trusts the leftmost, client-supplied X-Forwarded-For value instead of the client IP appended by a reverse proxy. Attackers can send forged X-Forwarded-For values through appending proxies to bypass per-IP rate limits on login, one-time passcode, and password validation endpoints, enabling brute-force attacks, and to falsify IP addresses recorded in audit logs.
Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a user enumeration vulnerability because userpassword.Compare() substitutes a placeholder hash derived from the string "hunter2" when a stored password hash is empty. Unauthenticated attackers can submit logins with the password "hunter2" and distinguish HTTP 403 from 401 responses to enumerate valid accounts and reveal the authentication provider of SSO-only users.
Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a stored HTML injection vulnerability because the ApplicationName and LogoURL appearance settings are rendered into HTML output without sufficient escaping. Attackers with the Owner role can store HTML markup in these settings that renders in the Coder dashboard and in SMTP notification emails sent to other deployment users.
Coder from 2.0.0 before 2.34.8 contains an open redirect vulnerability in handleAPIKeySmuggling that allows attackers to redirect users externally via unsanitized r.URL.Path values. Attackers can craft links on trusted workspace app subdomains with paths beginning with double slashes, which become scheme-relative redirects to attacker sites for phishing.