CVE-2023-32156 is a high severity firmware signature validation bypass, scored 8.8, in the Tesla Model 3 gateway. After privileged code execution on the infotainment system, an attacker on the vehicle network could run code on the gateway ECU. ZDI says firmware 2023.12 fixes it.
What's affected
The NVD record, dated 2024-05-03, covers Tesla Model 3 firmware, listing release 2023.6 in its product data. The flaw is in the handling of firmware updates: improper error handling during the update process lets an attacker execute code in the context of the Gateway ECU. The weakness types are CWE-367 (time-of-check time-of-use race condition). The record vector is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, scored 8.8.
Zero Day Initiative advisory ZDI-23-972 (ZDI-CAN-20734) says the issue is fixed in the 2023.12 firmware release. It was reported to the vendor on 2023-03-30 and published on 2023-07-18 after coordinated disclosure.
The advisory says an attacker must first obtain the ability to execute privileged code on the Tesla infotainment system, so this is a step in a chain, not an entry point.
The sources differ on severity. The NVD record scores it 8.8 (High), AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. ZDI scores it 9.0, which would fall in the Critical band, using AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (low privileges required, changed scope). This post titles the issue High to match the NVD record and tells you about the ZDI figure so you can judge for yourself.
No source says this flaw is exploited in the wild, and it is not in the CISA Known Exploited Vulnerabilities catalog.
How to check if you're exposed
Tesla delivers vehicle fixes as firmware releases. Check the software version shown on the vehicle's touchscreen, in the software information area of the controls menu, and compare it with the release named above.
If the car is not on a fixed release, make sure it is connected to a trusted Wi-Fi network or cellular service so it can receive updates, and install any pending update when the car prompts you. The advisory describes the flaw as requiring a prior foothold, so a fixed release matters most for cars that connect to untrusted Wi-Fi or pair with unknown Bluetooth devices.
The sources give no workaround besides updating.
What to do now
- Confirm each Model 3 you manage is on firmware 2023.12 or later. Fleet owners should record the version for every vehicle.
- Install any pending vehicle update promptly rather than postponing it.
- Avoid joining unknown Wi-Fi networks and avoid pairing unfamiliar Bluetooth devices, since the advisory describes attacks that begin from those paths.
- Treat the vehicle as a connected computer in your asset list, with an owner and an update routine.
- If a vehicle cannot update, contact Tesla service.
Why it matters
CWE-367 is a race: a program checks a condition, then acts later, and the state changes between the two. The ZDI text describes the update path as having improper error handling. Whatever the exact sequence, an update system that can be talked out of verifying a signature is a high value target, because the gateway ECU sits between the infotainment system and other parts of the vehicle network. Safeguard offers a free in-browser dependency scan at gold.safeguard.sh/scan for the packages in your own code. It does not inspect vehicle firmware or installed desktop applications, so those need a separate inventory.
Quick check
Why does this have two severity ratings?
NVD says 8.8 and ZDI says 9.0. They differ on the privileges required and on scope. Treat the issue as serious either way.
What does the attacker need first?
Privileged code execution on the Tesla infotainment system, per the advisory.
Sources
Last reviewed: 19 October 2026.