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

Louis Vuitton
2 Rue du Pont Neuf, Paris, 75001, FR
Last Update: 01/04/2026
For more than 150 years, men and women at Louis Vuitton have shared the same spirit of excellence and passion, reaffirming their expertise every day, the world over. With us, every career is a journey, filled with excitement and challenge, desire and daring. There is no...
Compliance Ranges Comparison

Van Cleef & Arpels







Louis Vuitton






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)
Louis Vuitton has 8.26% 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 - Louis Vuitton (X = Date, Y = Severity)
Louis Vuitton cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Van Cleef & Arpels

Louis Vuitton
FAQ
Latest Global CVEs
clash-verge-service-ipc before 2.3.0 has a world-reachable IPC endpoint, leading to local privilege escalation.
A vulnerability was identified in theonedev onedev up to 15.0.5. This vulnerability affects the function canAccessIssue of the file /issues/ of the component Pull Request Handler. Such manipulation of the argument issue leads to improper authorization. It is possible to launch the attack remotely. Upgrading to version 15.0.6 is able to resolve this issue. It is advisable to upgrade the affected component.
A vulnerability was determined in theonedev onedev up to 15.0.5. This affects an unknown part of the file /repositories/{projectId}/default-branch of the component REST API. This manipulation of the argument project.defaultBranch causes improper authorization. It is possible to initiate the attack remotely. Upgrading to version 15.0.6 is able to mitigate this issue. Upgrading the affected component is advised.
A vulnerability was found in theonedev onedev up to 15.0.5. Affected by this issue is some unknown functionality of the file /projects/ of the component Parent Project Handler. The manipulation of the argument project.parentId results in improper authorization. The attack may be performed from remote. Upgrading to version 15.0.6 can resolve this issue. It is recommended to upgrade the affected component.
A vulnerability has been found in theonedev onedev up to 15.0.5. Affected by this vulnerability is an unknown functionality of the file /projects. The manipulation of the argument project.forkedFromId leads to improper authorization. The attack is possible to be carried out remotely. Upgrading to version 15.0.6 addresses this issue. Upgrading the affected component is recommended.