Comparison Overview
Hot Topic

Hot Topic
18305 E. San Jose Ave, City of Industry, 91748, US
Last Update: 05/04/2026
At Hot Topic we pride ourselves on being the destination of pop culture and music merchandise. We do this by hiring the best people, having the best product, and providing the best customer experience for our one-of-a-kind fans. Founded in 1989 in a Southern California...

Chewy
7700 W Sunrise Blvd, Plantation, 33322, US
Last Update: 01/04/2026
At Chewy, our mission is to be the most trusted and convenient destination for pet parents and partners, everywhere. We view pets and pet parents as family and are obsessed with meeting their needs and exceeding customer expectations through every interaction. Behind ...
Compliance Ranges Comparison

Hot Topic







Chewy






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

Hot Topic

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