Comparison Overview
Alexis Bittar

Alexis Bittar
86 34th Street, Brooklyn, NY, 11232, US
Last Update: 01/06/2026
Brooklyn born and bred designer, Alexis Bittar has been designing jewelry for over 20 years. He began his illustrious career by selling on the streets of New York City in the early 1980s. Bittar sold his hand crafted pieces from a wooden fold-out table on St Marks Place...

Gucci
Via Don Lorenzo Perosi, 6, Casellina di Scandicci, 50018, IT
Last Update: 03/04/2026
Founded in Florence, Italy in 1921, Gucci is one of the world’s leading luxury brands. Following the House’s centenary, Gucci forges ahead continuing to redefine fashion and luxury while celebrating creativity, Italian craftsmanship, and innovation. Gucci is part of th...
Compliance Ranges Comparison

Alexis Bittar







Gucci






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

Alexis Bittar

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