Comparison Overview
LensCrafters

LensCrafters
Cincinnati, Ohio, US, 45202
Last Update: 21/03/2026
LensCrafters is a place for visionaries. We’ve got a vision for pairing state-of-the-art technology with a truly personal approach to eye care. Everything we do is centered around sight. Because quality care helps us see the joy in life. Because learning from the best...

Tommy Hilfiger
Danzigerkade 165, Amsterdam, North Holland, NL, 1013
Last Update: 05/08/2026
TOMMY HILFIGER is one of the world’s leading designer lifestyle brands creating a platform that inspires the modern American spirit, while committing to wasting nothing and welcoming all. Founded in 1985, Tommy Hilfiger delivers premium styling, quality and value to c...
Compliance Ranges Comparison

LensCrafters







Tommy Hilfiger






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

LensCrafters

Tommy Hilfiger
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.