Comparison Overview
Hublot

Hublot
N/A
Last Update: 23/02/2026
Founded in Switzerland in 1980, HUBLOT is defined by its innovation, which began with the highly original combination of gold and rubber. This "Art of Fusion" stems from the imagination of its visionary Chairman, Jean-Claude Biver, and has been driven forward by CEO Ric...

Hermès
24, rue du Faubourg-Saint-Honoré, Paris, 75008, FR
Last Update: 07/10/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

Hublot







Hermès






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Hublot in 2026.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Hermès in 2026.
Incident History - Hublot (X = Date, Y = Severity)
Hublot 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

Hublot

Hermès
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.