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.
CVE-2026-58459
This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 1.8%, top 23% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.6
- EG Score
- 9.6(medium)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity96% × 45%Exploitation2% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 2%
- EPSS %ILE
- 77%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 28, 2026
Advisory Details (5)
Auto-updated Aug 23, 2026gpsd gpsprof Command Injection via gnuplot plot title subtype field | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gpsd-gpsprof-command-injection-via-gnuplot-plot-title-subtype-fieldcommit 4c06658e988f (ntpsec/gpsd)
Fix landed in ntpsec/gpsd commit 4c06658e988f — awaiting tagged release
https://github.com/ntpsec/gpsd/commit/4c06658e988f4ced1a7a574ce082a22ef625df56commit 1a6bb7bcbdf5 (ntpsec/gpsd)
Fix landed in ntpsec/gpsd commit 1a6bb7bcbdf5 — awaiting tagged release
https://github.com/ntpsec/gpsd/commit/1a6bb7bcbdf58aa940132e630870af061dc88537commit 5581ba196d82 (ntpsec/gpsd)
Fix landed in ntpsec/gpsd commit 5581ba196d82 — awaiting tagged release
https://github.com/ntpsec/gpsd/commit/5581ba196d826a984fbfaf792b7d58535f9911cegpsprof gnuplot command injection via attacker-controlled GPS metadata (#404) · Issues · gpsd / gpsd · GitLab
https://gitlab.com/gpsd/gpsd/-/work_items/404#note_3534119267Vendor Advisories for CVE-2026-58459(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | gpsd-minimal-1:3.26.1-2.el9_8.1 | 2026-08-06 | redhat |
| redhat | gpsd-1:3.26.1-3.el10_2.1 | 2026-08-06 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gpsd | 3.22-4 ... 3.27.5-1 (17 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gpsd | 3.22-4.1 ... 3.27.5-1 (16 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gpsd | 3.25-5 ... 3.27.5-1 (8 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gpsd | 3.25-5, 3.26.1-1, 3.27-1, 3.27-1.1, 3.27.5-0.1 | 3.27.5-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 53× in last 7d / 334× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 425 total refreshes for this CVE.
- 2026-08-30 06:46 UTCEG score recompute
- 2026-08-30 06:46 UTCVendor advisory
- 2026-08-30 06:46 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 02:41 UTCVendor advisory
- 2026-08-28 02:41 UTCGHSA enrichment
- 2026-08-27 21:45 UTCEG score recompute
- 2026-08-27 21:45 UTCVendor advisory
- 2026-08-27 21:45 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 01:01 UTCEG score recompute
- 2026-08-27 01:01 UTCVendor advisory
- 2026-08-27 01:01 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 12:55 UTCVendor advisory
- 2026-08-26 12:55 UTCGHSA enrichment
- 2026-08-26 08:19 UTCVendor advisory
- 2026-08-26 08:19 UTCGHSA enrichment
- 2026-08-26 03:50 UTCVendor advisory
- 2026-08-26 03:50 UTCGHSA enrichment
- 2026-08-25 15:54 UTCEG score recompute
- 2026-08-25 15:54 UTCVendor advisory
- 2026-08-25 15:54 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-25 11:36 UTCVendor advisory
- 2026-08-25 11:36 UTCGHSA enrichment
- 2026-08-25 07:41 UTCVendor advisory
- 2026-08-25 07:41 UTCGHSA enrichment
- 2026-08-25 03:50 UTCVendor advisory
- 2026-08-25 03:50 UTCGHSA enrichment
- 2026-08-25 00:05 UTCVendor advisory
- 2026-08-25 00:05 UTCGHSA enrichment
- 2026-08-24 20:20 UTCEG score recompute
- 2026-08-24 20:20 UTCVendor advisory
- 2026-08-24 20:20 UTCGHSA enrichment
- 2026-08-24 13:22 UTCVendor advisory
- 2026-08-24 13:22 UTCGHSA enrichment
- 2026-08-24 09:36 UTCEG score recompute
- 2026-08-24 09:36 UTCVendor advisory
- 2026-08-24 09:36 UTCGHSA enrichment
- 2026-08-24 03:59 UTCVendor advisory
- 2026-08-24 03:59 UTCGHSA enrichment
- 2026-08-24 00:06 UTCVendor advisory
- 2026-08-24 00:06 UTCGHSA enrichment
- 2026-08-23 20:21 UTCVendor advisory
- 2026-08-23 20:21 UTCGHSA enrichment
- 2026-08-23 16:35 UTCVendor advisory
- 2026-08-23 16:35 UTCGHSA enrichment
- 2026-08-23 12:50 UTCVendor advisory
- 2026-08-23 12:50 UTCGHSA enrichment
- 2026-08-23 09:05 UTCVendor advisory
- 2026-08-23 09:05 UTCGHSA enrichment
- 2026-08-23 05:19 UTCVendor advisory
- 2026-08-23 05:19 UTCGHSA enrichment
- 2026-08-23 01:29 UTCEG score recompute
- 2026-08-23 01:29 UTCVendor advisory
- 2026-08-23 01:29 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 21:35 UTCVendor advisory
- 2026-08-22 21:35 UTCGHSA enrichment
- 2026-08-22 17:34 UTCVendor advisory
- 2026-08-22 17:34 UTCGHSA enrichment
- 2026-08-22 12:39 UTCVendor advisory
- 2026-08-22 12:39 UTCGHSA enrichment
- 2026-08-22 08:54 UTCVendor advisory
- 2026-08-22 08:54 UTCGHSA enrichment
- 2026-08-22 05:08 UTCVendor advisory
- 2026-08-22 05:08 UTCGHSA enrichment
- 2026-08-22 01:23 UTCEG score recompute
- 2026-08-22 01:23 UTCVendor advisory
- 2026-08-22 01:23 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 21:38 UTCVendor advisory
- 2026-08-21 21:38 UTCGHSA enrichment
- 2026-08-21 17:53 UTCVendor advisory
- 2026-08-21 17:53 UTCGHSA enrichment
- 2026-08-21 14:08 UTCVendor advisory
- 2026-08-21 14:08 UTCGHSA enrichment
- 2026-08-21 10:12 UTCVendor advisory
- 2026-08-21 10:12 UTCGHSA enrichment
- 2026-08-21 06:27 UTCVendor advisory
- 2026-08-21 06:27 UTCGHSA enrichment
- 2026-08-21 02:42 UTCVendor advisory
- 2026-08-21 02:42 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEG score recompute
- 2026-08-20 22:56 UTCVendor advisory
- 2026-08-20 22:56 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 19:02 UTCVendor advisory
- 2026-08-20 19:02 UTCGHSA enrichment
- 2026-08-20 15:17 UTCVendor advisory
- 2026-08-20 15:16 UTCGHSA enrichment
- 2026-08-20 09:18 UTCVendor advisory
- 2026-08-20 09:18 UTCGHSA enrichment
- 2026-08-20 05:33 UTCVendor advisory
- 2026-08-20 05:33 UTCGHSA enrichment
- 2026-08-20 01:48 UTCEG score recompute
- 2026-08-20 01:48 UTCVendor advisory
- 2026-08-20 01:48 UTCGHSA enrichment
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(5)
What is CVE-2026-58459?
When was CVE-2026-58459 disclosed?
Is CVE-2026-58459 actively exploited?
What is the CVSS score of CVE-2026-58459?
How do I remediate CVE-2026-58459?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58459
Is Your Infrastructure Affected by CVE-2026-58459?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.