Comparison Overview
Piaget

Piaget
37 chemin du champs des filles, Plan-les-Ouates, Geneva, 1228, CH
Last Update: 03/02/2026
Piaget epitomizes daring creativity – a quality that has continued to permeate through the Maison since its beginnings in 1874. From his first workshop in La Côte-aux- Fées, Georges-Edouard Piaget devoted himself to crafting high-precision movements in a feat that forme...

Christian Dior Couture
30 avenue Montaigne, Paris, 75008, FR
Last Update: 13/08/2026
Welcome to Christian Dior Couture, House of Dreams, House of Talents. Christian Dior was the designer of dreams. In founding his House in 1947, marked by the revolution of the New Look, he metamorphosed his reveries into wonderful creations. His visionary spirit never ...
Compliance Ranges Comparison

Piaget







Christian Dior Couture






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

Piaget

Christian Dior Couture
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.