Comparison Overview
Sunglass Hut

Sunglass Hut
Piazzale Cadorna 3, Milano, 20123, IT
Last Update: 06/02/2026
When you enter Sunglass Hut, you enter the House of Sun. You’ll bring warmth into the hearts and souls of our customers and the world we live in. We know our products are incredible, but that it’s your spirit that makes our customers love coming back. At Sunglass Hu...

Forever 21
3880 Mission Road, Los Angeles, 90031, US
Last Update: 02/04/2026
Forever 21 continues to be a fashion industry leader with a mission to make the latest trends accessible to all. F21 persists on staying ahead of innovation and providing styles and fit that our customers love. While reinventing for now and beyond, we’re seeking passion...
Compliance Ranges Comparison

Sunglass Hut







Forever 21






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Sunglass Hut in 2026.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Forever 21 in 2026.
Incident History - Sunglass Hut (X = Date, Y = Severity)
Sunglass Hut cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Forever 21 (X = Date, Y = Severity)
Forever 21 cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sunglass Hut

Forever 21
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.