# CVE-2025-2082: Tesla Model 3 VCSEC Integer Overflow Remote Code Execution Vulnerability

> Network-adjacent attackers can execute arbitrary code on Tesla Model 3 vehicles by triggering an integer overflow in the VCSEC module via TPMS responses.

- **Severity:** High 7.5 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2025
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-h982-967r-m89p

## What is CVE-2025-2082?

CVE-2025-2082 is a high-severity vulnerability in Tesla Model 3, published on 30 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Tesla Model 3 VCSEC Integer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected Tesla Model 3 vehicles. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the VCSEC module. By manipulating the certificate response sent from the Tire Pressure Monitoring System (TPMS), an attacker can trigger an integer overflow before writing to memory. An attacker can leverage this vulnerability to execute code in the context of the VCSEC module and send arbitrary messages to the vehicle CAN bus. Was ZDI-CAN-23800.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-2082?

It affects 1 product.


Products: Tesla Model 3 Firmware.

## How do I fix CVE-2025-2082?

No fix has been published for CVE-2025-2082 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2082 being exploited?

There is no known exploitation of CVE-2025-2082 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Burak1320demiroz/cve-2025-2082 (github_poc): https://github.com/Burak1320demiroz/cve-2025-2082
- https://github.com/shirabo/cve-2025-2082-POV (github_poc): https://github.com/shirabo/cve-2025-2082-POV

## Other vulnerabilities in Tesla Model 3

- [CVE-2023-32156](https://insights.sbomify.com/CVE-2023-32156/): Tesla Model 3 Gateway Firmware Signature Validation Bypass Vulnerability (critical 9.0)
- [CVE-2022-42430](https://insights.sbomify.com/CVE-2022-42430/): Use after free in Model 3 (high 8.8)
- [CVE-2022-42431](https://insights.sbomify.com/CVE-2022-42431/): Memory corruption in Model 3 (high 8.8)
- [CVE-2019-9977](https://insights.sbomify.com/CVE-2019-9977/): Code injection in n/a (high 8.8)
- [CVE-2023-32155](https://insights.sbomify.com/CVE-2023-32155/): Tesla Model 3 bcmdhd Out-Of-Bounds Write Local Privilege Escalation Vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2082 and fix it if it is affected.

What it is: CVE-2025-2082 is a high-severity vulnerability in Tesla Model 3, published on 30 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2082 in the wild and no public exploit code.

Affected product: Tesla Model 3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2082/ (Markdown: https://insights.sbomify.com/CVE-2025-2082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2082
- OSV: https://osv.dev/vulnerability/CVE-2025-2082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2082/
Summaries are generated and may contain mistakes; the official description above is the record.