Honda is a global mobility company primarily known as a manufacturer of automobiles, motorcycles, power products and aircraft.
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.
Security & Compliance Standards Overview
No incidents recorded for Honda in 2025.
No incidents recorded for Li Auto in 2025.
Honda cyber incidents detection timeline including parent company and subsidiaries
Li Auto cyber incidents detection timeline including parent company and subsidiaries
Last 3 Security & Risk Events by Company
FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.
Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.
Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.
Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.
The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.
