Comparison Overview
Van Cleef & Arpels

Van Cleef & Arpels
75001, Place Vendôme, Paris, Île-de-France, 75001, FR
Last Update: 21/01/2026
Van Cleef & Arpels was born in Paris’ place Vendôme in 1906, following Alfred Van Cleef’s marriage to Estelle Arpels in 1895. For over a century, their names have graced some of the finest High Jewelry ever created. Over the years, the Maison has remained faithful to a...

LVMH
22, avenue Montaigne, Paris, 75008, FR
Last Update: 01/04/2026
LVMH is the world leader in luxury. A family group founded in 1987 and headed by Chairman and CEO Bernard Arnault, LVMH is now home to 75 iconic Maisons, which embody a distinctive art de vivre blending heritage and modernity. With reported sales of 86.2 billion euros ...
Compliance Ranges Comparison

Van Cleef & Arpels







LVMH






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

Van Cleef & Arpels

LVMH
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.