dbcve.org
GpsdApplication · Gpsd Project

CVE-2026-58459

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to after 3.27.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
gpsd through release-3.27.5, fixed at commit 4c06658, contains a command injection vulnerability in gpsprof that allows attackers who control the GPS device subtype value to execute arbitrary shell commands by embedding backtick payloads in the gnuplot plot title without proper escaping. The subtype field sourced from a DEVICES JSON log entry or NMEA PGRMT sentence is written into a generated gnuplot program via a set title statement with only double-quote characters escaped, enabling arbitrary shell command execution as the user running gnuplot when the victim renders the generated plot through the gpsprof and gnuplot workflow.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

gpsd's gpsprof tool contains a command injection vulnerability where the GPS device subtype value (sourced from DEVICES JSON log entries or NMEA PGRMT sentences) is embedded into a generated gnuplot program via a 'set title' statement. Only double-quote characters are escaped, allowing attackers to inject backtick payloads that execute arbitrary shell commands as the user running gnuplot when rendering plots.

MitigationUpgrade to gpsd version containing commit 4c06658 or later. Avoid processing untrusted GPS device data through gpsprof until patched, and disable or sandbox the gnuplot workflow if possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GpsdApplication
Affected:<= 3.27.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify gpsd version
    Run 'gpsd --version' or check your package manager for gpsd version (e.g., 'dpkg -l gpsd', 'rpm -qi gpsd', or 'pkg info gpsd')
    Affected if The installed version is 3.27.5 or lower
  2. Locate gpsprof binary
    Run 'which gpsprof' or search for gpsprof in common binary paths (/usr/bin/gpsprof, /usr/local/bin/gpsprof)
    Affected if The gpsprof tool exists on the system and is executable by your user account
  3. Check for gnuplot availability
    Run 'which gnuplot' to determine if gnuplot is installed and accessible
    Affected if gnuplot is installed and available to be invoked by gpsprof
  4. Identify DEVICES log or NMEA PGRMT input sources
    Review your gpsd configuration and any scripts that process GPS data logs. Search for files containing 'DEVICES' JSON entries or NMEA '$PGRMT' sentences that may feed into gpsprof
    Affected if Your gpsd or logging workflow processes DEVICES JSON logs or NMEA PGRMT sentences from untrusted sources through gpsprof

You are affected if you run gpsd version 3.27.5 or lower, have the gpsprof tool available, use gnuplot, and process GPS device subtype data from DEVICES logs or PGRMT sentences through gpsprof.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.27.5
Vendor patch github.com →
Interim mitigation

Upgrade to gpsd version containing commit 4c06658 or later. Avoid processing untrusted GPS device data through gpsprof until patched, and disable or sandbox the gnuplot workflow if possible.

Recommended fix High confidence

Any gpsd version newer than 3.27.5 that includes commit 4c06658 (the fix commit)

  1. 1. Identify the current installed gpsd version using 'gpsd --version' or checking your package manager
  2. 2. Navigate to the gpsd GitHub repository at https://github.com/ntpsec/gpsd
  3. 3. Check the commit history for commit 4c06658 to verify it contains the fix for the command injection in gpsprof
  4. 4. Either: a) Upgrade to the latest gpsd release that includes commit 4c06658, or b) Build from source at the specific commit 4c06658
  5. 5. If upgrading via package manager, wait for your distribution to package a version newer than 3.27.5 that includes the fix
  6. 6. After upgrade, verify the version includes the patch by checking release notes or git log
  7. 7. Ensure any DEVICES JSON log entries or NMEA PGRMT sentences from untrusted sources are not processed until the fix is applied
Caveat Minor: Upgrading gpsd may introduce changes to configuration syntax or dependencies; review release notes for any breaking changes between 3.27.5 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gpsd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58459 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58459 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data