Skip to main content
Mallory
HighVulnerability

CVE-2025-2082: Remote Code Execution in Tesla Model 3 VCSEC via TPMS Certificate Response Integer Overflow

Published Apr 30, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3
EPSS0.38%33rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Tesla
IdentifiersCVE-2025-2082CWE-190 · Integer Overflow or Wraparound

CVE-2025-2082 is a remote code execution vulnerability affecting the VCSEC module in Tesla Model 3 vehicles. The flaw is caused by an integer overflow that occurs before a memory write when the VCSEC component processes a certificate response originating from the Tire Pressure Monitoring System (TPMS). A network-adjacent attacker can manipulate the TPMS certificate response to trigger the overflow and corrupt memory, ultimately achieving arbitrary code execution in the context of the VCSEC module. The issue is identified as ZDI-CAN-23800.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a network-adjacent, unauthenticated attacker to execute arbitrary code within the VCSEC module on an affected Tesla Model 3. Because the compromised module can send arbitrary messages to the vehicle CAN bus, the vulnerability can enable unauthorized interaction with in-vehicle systems and potentially broader safety, integrity, and operational impacts depending on reachable CAN functions and existing vehicle trust boundaries.

Mitigation

If you can’t patch tonight, do this now.

Where immediate patching is not possible, reduce exposure to network-adjacent attack paths involving the TPMS-to-VCSEC communication path and apply vendor updates as soon as available. Because the available content does not provide validated temporary workarounds or configuration-based mitigations, no specific mitigation beyond prompt vendor patching can be stated with confidence.

Remediation

Patch, then assume compromise.

Tesla has previously addressed this vulnerability in its products, but the specific fixed software or firmware version is not provided in the available content. Remediation is to apply the vendor-provided update that fixes CVE-2025-2082/ZDI-CAN-23800 to affected Tesla Model 3 vehicles.

Public exploits

Exploits

No validated public exploits yet. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
TeslaModel 3 Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2025-2082 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-2082 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-2082?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-2082.
Is there a patch for CVE-2025-2082?
Tesla has previously addressed this vulnerability in its products, but the specific fixed software or firmware version is not provided in the available content. Remediation is to apply the vendor-provided update that fixes CVE-2025-2082/ZDI-CAN-23800 to affected Tesla Model 3 vehicles.
What products are affected by CVE-2025-2082?
Tesla Model 3 Firmware.
How severe is CVE-2025-2082?
CVE-2025-2082 has a CVSS v3 score of 7.5 (High) and an EPSS score of 0.38% (33rd percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.