Comparison Overview

Honda

VS

Li Auto

Honda

2-1-1 Minamiaoyama Minato-ku, Tokyo 107-8556, JP
Last Update: 2025-12-10
Between 800 and 849

Honda is a global mobility company primarily known as a manufacturer of automobiles, motorcycles, power products and aircraft.

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Li Auto

Number 11 of Wenliang Street, Shunyi District, None, Beijing, Beijing, CN, 101399
Last Update: 2025-12-09
Between 750 and 799

Li Auto Inc. is a leader in China's new energy vehicle market. The Company designs, develops, manufactures, and sells premium smart electric vehicles. Its mission is: Create a Mobile Home, Create Happiness (创造移动的家,创造幸福的家). Through innovations in product, technology, and business model, the Company provides families with safe, convenient, and comfortable products and services. Li Auto is a pioneer in successfully commercializing extended-range electric vehicles in China. While firmly advancing along this technological route, it builds platforms for battery electric vehicles in parallel. The Company leverages technology to create value for users. It concentrates its in-house development efforts on proprietary range extension systems, innovative electric vehicle technologies, and smart vehicle solutions. The Company started volume production in November 2019. Its current model lineup includes Li MEGA, a high-tech flagship family MPV, Li L9, a six-seat flagship family SUV, Li L8, a six-seat premium family SUV, Li L7, a five-seat flagship family SUV, and Li L6, a five-seat premium family SUV. The Company will continue to expand its product lineup to target a broader user base.

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 1,666
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/honda.jpeg
Honda
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/理想汽车.jpeg
Li Auto
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Honda
100%
Compliance Rate
0/4 Standards Verified
Li Auto
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for Honda in 2025.

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for Li Auto in 2025.

Incident History — Honda (X = Date, Y = Severity)

Honda cyber incidents detection timeline including parent company and subsidiaries

Incident History — Li Auto (X = Date, Y = Severity)

Li Auto cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/honda.jpeg
Honda
Incidents

No Incident

https://images.rankiteo.com/companyimages/理想汽车.jpeg
Li Auto
Incidents

No Incident

FAQ

Honda company demonstrates a stronger AI Cybersecurity Score compared to Li Auto company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Li Auto company has disclosed a higher number of cyber incidents compared to Honda company.

In the current year, Li Auto company and Honda company have not reported any cyber incidents.

Neither Li Auto company nor Honda company has reported experiencing a ransomware attack publicly.

Neither Li Auto company nor Honda company has reported experiencing a data breach publicly.

Neither Li Auto company nor Honda company has reported experiencing targeted cyberattacks publicly.

Neither Honda company nor Li Auto company has reported experiencing or disclosing vulnerabilities publicly.

Neither Honda nor Li Auto holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Honda company nor Li Auto company has publicly disclosed detailed information about the number of their subsidiaries.

Honda company employs more people globally than Li Auto company, reflecting its scale as a Motor Vehicle Manufacturing.

Neither Honda nor Li Auto holds SOC 2 Type 1 certification.

Neither Honda nor Li Auto holds SOC 2 Type 2 certification.

Neither Honda nor Li Auto holds ISO 27001 certification.

Neither Honda nor Li Auto holds PCI DSS certification.

Neither Honda nor Li Auto holds HIPAA certification.

Neither Honda nor Li Auto holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

Risk Information
cvss3
Base: 8.1
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Risk Information
cvss3
Base: 2.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Description

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

Risk Information
cvss3
Base: 4.5
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
Description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N