Comparison Overview
TVS Motor Company

TVS Motor Company
Hosur, Tamil Nadu , Hosur, 635109, IN
Last Update: 03/04/2026
TVS Motor Company is a reputed two and three-wheeler manufacturer globally, championing progress through Mobility with a focus on sustainability. Rooted in our 100-year legacy of Trust, Value, and Passion for Customers and Exactness, we take pride in making internationa...

LEONI
Marienstraße 5, Nürnberg, 90402, DE
Last Update: 01/04/2026
LEONI is a global provider of products, solutions and services for energy and data management in the automotive industry. The group of companies has around 87,000 employees in 21 countries and generated consolidated sales of EUR 5 billion in 2024. The partnership betwee...
Compliance Ranges Comparison

TVS Motor Company







LEONI






Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for TVS Motor Company in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for LEONI in 2026.
Incident History - TVS Motor Company (X = Date, Y = Severity)
TVS Motor Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - LEONI (X = Date, Y = Severity)
LEONI cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

TVS Motor Company

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