Comparison Overview
Jaquet Droz

Jaquet Droz
Allée du Tourbillon 2, La Chaux-de-Fonds, 2300, CH
Last Update: 20/03/2026
Pierre Jaquet-Droz was one of the greatest craftsmen of the 18th century. Born in La Chaux-de-Fonds in 1721, he was a master watchmaker of genius and vision who marked the history of his profession. Since Jaquet Droz joined the Swatch Group in 2000, it has continued its...

Swatch Group
Seevorstadt 6, Biel, Berne, CH, 2502
Last Update: 01/04/2026
Swatch Group is the world's number one manufacturer of finished watches. With its 16 watch brands, the Group is present in all price segments, and is also active in the manufacture and sale of jewelry, watch movements and components. Swatch Group unites, among other co...
Compliance Ranges Comparison

Jaquet Droz







Swatch Group






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Jaquet Droz in 2026.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Swatch Group in 2026.
Incident History - Jaquet Droz (X = Date, Y = Severity)
Jaquet Droz cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Swatch Group (X = Date, Y = Severity)
Swatch Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Jaquet Droz

Swatch Group
FAQ
Latest Global CVEs
The GOOSE subscriber component improperly validates the UTC timestamp field in unauthenticated IEC 61850 GOOSE (EtherType 0x88B8) Layer-2 multicast messages. A specially crafted GOOSE frame containing an undersized timestamp field can trigger a heap out-of-bounds read during message processing, causing the process to crash and resulting in a denial-of-service condition.
OpenClaw Dashboard contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to execute arbitrary JavaScript in the administrator's browser session by injecting HTML markup into agent transcript messages processed through the sessions API. Attackers can craft a message containing inline event handler payloads such as an img tag with an onerror attribute within the 60-character rendering budget, which is stored in the session transcript and interpolated unsanitized into innerHTML on the default landing page, allowing theft of session tokens and unauthorized calls to authenticated administrative endpoints including agent instruction file modification.
MeshCentral 1.1.21 contains a cross-site WebSocket hijacking protection bypass vulnerability that allows unauthenticated remote attackers to hijack authenticated administrator sessions by exploiting an unconditional early return in the CheckWebServerOriginName() function within webserver.js when self-signed certificates are in use. Attackers can open cross-origin WebSocket connections to any of the twelve WebSocket endpoints, send crafted action commands to exfiltrate the server sessionKey used to sign session cookies, forge session tokens as arbitrary users, and gain full remote control of all managed devices governed by the MeshCentral instance.
The GOOSE parser contains an off-by-one boundary-handling flaw that can be triggered by a single unauthenticated Layer-2 multicast frame on the process bus. When specific GOOSE message fields are processed, the parser advances its internal buffer position incorrectly, resulting in a heap out-of-bounds read. On affected platforms, this condition reliably terminates the subscriber process and causes a denial-of-service.
The GOOSE payload parser contains a boundary handling flaw that can be triggered by a single unauthenticated Layer 2 multicast frame on the process bus. When processing specific payload fields, an attacker controlled inner element length may exceed its enclosing length, causing the parser to over read by one byte. This out-of-bounds read reliably terminates the subscriber process, resulting in a denial-of-service condition.