Comparison Overview
Tata Health

Tata Health
HSR Layout Junction, Bengaluru, IN
Last Update: 20/03/2026
TATA Health is part of Tata Industries and is the Digital Health arm of the TATA group, setup with the vision of providing predictive, preventive, and personalised healthcare to consumers. It offers a full suite of health services including instant doctor consultation s...

Purpose Brands, LLC
111 Weir Drive, Woodbury, 55125, US
Last Update: 29/03/2026
Purpose Brands, LLC provides fitness, nutrition and wellness support and services to more than 7,000 communities and millions of people around the world. We own and operate the world’s largest and most trusted portfolio of fitness, health and wellness franchise brand...
Compliance Ranges Comparison

Tata Health







Purpose Brands, LLC






Benchmark & Cyber Underwriting Signals
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Tata Health in 2026.
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Purpose Brands, LLC in 2026.
Incident History - Tata Health (X = Date, Y = Severity)
Tata Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Purpose Brands, LLC (X = Date, Y = Severity)
Purpose Brands, LLC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Tata Health

Purpose Brands, LLC
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.