Comparison Overview
Target Optical

Target Optical
420 Fifth Avenue, New York, NY 10018, New York, NY, US, 10018
Last Update: 02/04/2026
At Target Optical, we love the neighborhoods we belong to and that’s why we care for them. By listening and building relationships with one another, we help our guests get quality eye care products and services at a great value. We help people see more clearly and con...

The TJX Companies, Inc.
770 Cochituate Road, Framingham, 01701, US
Last Update: 06/08/2026
TJX is the leading off-price apparel and home fashions retailer in the U.S. and worldwide, with four global home offices, seven brands, nearly 4,700 stores in nine countries, and five distinctive branded e-commerce sites. As Associates, we make a difference with our con...
Compliance Ranges Comparison

Target Optical







The TJX Companies, Inc.






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

Target Optical

The TJX Companies, Inc.
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.