Comparison Overview
Longines Watch Co. Francillon Ltd.

Longines Watch Co. Francillon Ltd.
Rue des Noyettes 8, Saint-Imier, 2610, CH
Last Update: 14/03/2026
Based in Saint-Imier in Switzerland since 1832, the watchmaking company Longines wields expertise steeped in tradition, elegance and performance. With generations of experience as official timekeeper of world championships, and as partner of international sports federat...

Hermès
24, rue du Faubourg-Saint-Honoré, Paris, 75008, FR
Last Update: 29/05/2026
A creator, artisan and seller of high-quality objects since 1837, Hermès is an independent, family-owned French house that employs more than 16,600 people worldwide. Driven by its permanent entrepreneurial spirit and consistently high standards, Hermès cultivates the fr...
Compliance Ranges Comparison

Longines Watch Co. Francillon Ltd.







Hermès






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Longines Watch Co. Francillon Ltd. in 2026.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Hermès in 2026.
Incident History - Longines Watch Co. Francillon Ltd. (X = Date, Y = Severity)
Longines Watch Co. Francillon Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hermès (X = Date, Y = Severity)
Hermès cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Longines Watch Co. Francillon Ltd.

Hermès
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.