Tesla Fleet Telemetry allows spoofing telemetry for arbitrary vehicles via compromised vehicle credentials
Priority LOW 38CWE-295Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-295.
Summary
### 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.
Why it matters now
Fix Fixed github.com/teslamotors/fleet-telemetry (Go): 0.9.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | github.com/teslamotors/fleet-telemetry (Go) | before 0.9.0 | 0.9.0 | Patch available | GHSA-prxj-3gcv-cqrh |
- github.com/teslamotors/fleet-telemetry (Go) Vendor— Affected before 0.9.0 Fixed in 0.9.0 Patch available GHSA-prxj-3gcv-cqrh
Remediation
- Fix · GHSA-prxj-3gcv-cqrh github.com/teslamotors/fleet-telemetry (Go) Fixed in 0.9.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-prxj-3gcv-cqrh
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences