Tesla Fleet Telemetry allows spoofing telemetry for arbitrary vehicles via compromised vehicle credentials

published 2026-04-01 7mo ago modified 2026-06-25 4mo ago also GO-2026-5553

cvss: 5.9; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### Summary A vulnerability in vehicle authentication allows threat actor with valid client credentials (i.e., a private key and certificate from a rooted infotainment system) to impersonate arbitrary VINs when authenticating to the telemetry server.

### Impact The attacker would be able to submit falsified telemetry records for arbitrary VINs.

Patch / fix

fixed in 1 links 1

go github.com/teslamotors/fleet-telemetry 0.9.0

github.com/teslamotors/fleet-telemetry@d5ca0da commit

Is GHSA-prxj-3gcv-cqrh in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	5.9	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
go	github.com/teslamotors/fleet-telemetry	<0.9.0	0.9.0

Classification

Weakness

CWE-295 Improper Certificate Validation

References

github.com /teslamotors/fleet-telemetry/commit/d5ca0dab55812029fd38eb77f079f74ce4f47286
web, patch
github.com /teslamotors/fleet-telemetry/security/advisories/GHSA-prxj-3gcv-cqrh
web, advisory
github.com /teslamotors/fleet-telemetry
package

Sources

GitHub Advisory GHSA-prxj-3gcv-cqrh
OSV GO-2026-5553

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.