Comparison Overview
BorgWarner

BorgWarner
3850 Hamlin Rd, Auburn Hills, Michigan, US, 48326
Last Update: 01/04/2026
As a global product leader for over 130 years, we deliver innovative and sustainable mobility solutions. Guided by our commitment to inclusion, integrity, excellence, responsibility and collaboration—and our pledge to reach carbon neutrality by 2035—we’re leading the au...

Ashok Leyland
No.1 Sardar Patel Road, Guindy, Chennai, 600032, IN
Last Update: 20/09/2026
Ashok Leyland vehicles have built a reputation for reliability and ruggedness. The 5,00,000 vehicles we have put on the roads have considerably eased the additional pressure placed on road transportation in independent India. In the populous Indian metros, four out o...
Compliance Ranges Comparison

BorgWarner







Ashok Leyland






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

BorgWarner

Ashok Leyland
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)