Comparison Overview
Li Auto
Li Auto
Number 11 of Wenliang Street, Shunyi District, Beijing, Beijing, CN, 101399
Last Update: 24/05/2026
Founded on July. 1, 2015, Li Auto's brand mission is to "Be Proactive, Change the World". We are dedicated to providing families with safer, more comfortable, and more convenient smart EVs through breakthrough innovations in products, technologies, and business models. ...
Ashok Leyland
No.1 Sardar Patel Road, Guindy, Chennai, 600032, IN
Last Update: 02/04/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
Li Auto
Ashok Leyland
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Li Auto in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Ashok Leyland in 2026.
Incident History - Li Auto (X = Date, Y = Severity)
Li Auto 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
Li Auto
Ashok Leyland
FAQ
Latest Global CVEs
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an inadequate encryption strength vulnerability which could allow an attacker to steal admin credentials via weak hash or a pass-the-hash attack.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could allow for asset discovery by unauthenticated users.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow an attacker to use an active proxy, which would bypass OT segmentation.
Pronetiqs IntraVUE Versions 3.2.1a14 and prior have a plaintext storage of a password vulnerability that could expose cleartext credentials through the API.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could expose the underlying host/share filesystem.