How severe is GHSA-prxj-3gcv-cqrh?

GHSA-prxj-3gcv-cqrh has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-prxj-3gcv-cqrh?

GHSA-prxj-3gcv-cqrh affects the following packages: github.com/teslamotors/fleet-telemetry (Go). Ecosystems affected: Go.

How do I fix GHSA-prxj-3gcv-cqrh?

Update github.com/teslamotors/fleet-telemetry to 0.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-prxj-3gcv-cqrh is resolved across your whole dependency graph.

How do I detect GHSA-prxj-3gcv-cqrh in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/teslamotors/fleet-telemetry, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-prxj-3gcv-cqrh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-prxj-3gcv-cqrh?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-prxj-3gcv-cqrh can be triaged on real exposure rather than presence alone.

Is GHSA-prxj-3gcv-cqrh actively exploited in the wild?

No public exploit code has been indexed for GHSA-prxj-3gcv-cqrh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-prxj-3gcv-cqrh published, and has it been updated?

GHSA-prxj-3gcv-cqrh was published on April 1, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

GHSA-prxj-3gcv-cqrh — fleet-telemetry

MEDIUMFix: teslamotors/fleet-telemetry@d5ca0da

GHSA-prxj-3gcv-cqrh is a medium-severity (CVSS 5.9) vulnerability in github.com/teslamotors/fleet-telemetry. A fix is available for github.com/teslamotors/fleet-telemetry — see the affected versions and patch details below.

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

Also known asGO-2026-5553

Published

Apr 1, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/teslamotors/fleet-telemetry

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/teslamotors/fleet-telemetry`	all versions	0.9.0`go get github.com/teslamotors/fleet-telemetry@v0.9.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/teslamotors/fleet-telemetry, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/teslamotors/fleet-telemetry to 0.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-prxj-3gcv-cqrh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-prxj-3gcv-cqrh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-prxj-3gcv-cqrh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-prxj-3gcv-cqrh in your dependencies?

O3 Security finds GHSA-prxj-3gcv-cqrh across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works