CVE-2026-60122

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-23. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

gpsd through release-3.27.5, fixed at commit 4c06658, contains a code injection vulnerability in the gpsprof utility that allows an attacker who controls GPS input data to execute arbitrary OS commands by injecting malicious content into the SKY.satellites[].used field, which is inserted unsanitized into a gnuplot heredoc data block. Attackers can supply a used value containing the string EOD to terminate the heredoc early and append gnuplot system() calls, achieving OS command execution as the user running gpsprof when the generated plot script is processed by gnuplot in polar mode.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 23, 2026

Last Modified

July 30, 2026

Advisory Details (3)

Auto-updated Jul 23, 2026
Patch available.
Web page

gpsd gpsprof Code Injection via SKY.satellites used Field | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gpsd-gpsprof-code-injection-via-sky-satellites-used-field
Web page

clients/gpsprof.py.in: ensure sats.used is boolean. Issue 406 (5a9c44a4) · Commits · gpsd / gpsd · GitLab

https://gitlab.com/gpsd/gpsd/-/commit/5a9c44a42136b9bb98d460a8a716e9fd344a8d93
Web page

Gnuplot Data-Block EOD Injection in gpsprof Polar Mode (#406) · Issues · gpsd / gpsd · GitLab

https://gitlab.com/gpsd/gpsd/-/work_items/406

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgpsd-minimal-1:3.26.1-2.el9_8.22026-09-08redhat
redhatgpsd-1:3.26.1-3.el10_2.22026-09-08redhat

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)
PackageVulnerable rangeFix by version rangeDependents
gpsd3.22-4 ... 3.27.5-1 (17 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gpsd3.22-4.1 ... 3.27.5-3 (18 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
gpsd3.25-5, 3.25-5+deb13u1
  • every version up to 3.25-5+deb13u2: fixed in 3.25-5+deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
gpsd3.25-5, 3.26.1-1, 3.27-1, 3.27-1.1, 3.27.5-0.1
  • every version up to 3.27.5-1: fixed in 3.27.5-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 68× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 257 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 157 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-10-13 15:40 UTCEG score recompute
  3. 2026-10-13 15:40 UTCVendor advisory
  4. 2026-10-13 15:40 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  6. 2026-10-12 15:52 UTCEG score recompute
  7. 2026-10-11 19:35 UTCEG score recompute
  8. 2026-10-11 16:51 UTCEG score recompute
  9. 2026-10-11 14:13 UTCEG score recompute
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-10-04 08:19 UTCEG score recompute
  19. 2026-10-04 08:19 UTCVendor advisory
  20. 2026-10-04 08:19 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  22. 2026-10-03 03:24 UTCEG score recompute
  23. 2026-10-03 03:24 UTCVendor advisory
  24. 2026-10-03 03:24 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 16th percentile
Show 75 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  2. 2026-10-01 06:15 UTCEG score recompute
  3. 2026-10-01 06:15 UTCVendor advisory
  4. 2026-10-01 06:15 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  6. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  7. 2026-09-28 05:04 UTCEG score recompute
  8. 2026-09-28 05:04 UTCVendor advisory
  9. 2026-09-28 05:04 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-09-24 01:12 UTCEG score recompute
  12. 2026-09-24 01:12 UTCVendor advisory
  13. 2026-09-24 01:12 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-09-23 10:58 UTCVendor advisory
  16. 2026-09-23 10:58 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-09-22 22:42 UTCEG score recompute
  18. 2026-09-22 22:42 UTCVendor advisory
  19. 2026-09-22 22:42 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-20 01:46 UTCEG score recompute
  22. 2026-09-20 01:46 UTCVendor advisory
  23. 2026-09-20 01:46 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-09-18 22:30 UTCEG score recompute
  25. 2026-09-18 22:30 UTCVendor advisory
  26. 2026-09-18 22:30 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  27. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-09-18 03:03 UTCEG score recompute
  29. 2026-09-18 03:03 UTCVendor advisory
  30. 2026-09-18 03:03 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  31. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-17 02:01 UTCEG score recompute
  33. 2026-09-17 02:01 UTCVendor advisory
  34. 2026-09-17 02:01 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-09-16 06:45 UTCEG score recompute
  37. 2026-09-16 06:45 UTCVendor advisory
  38. 2026-09-16 06:45 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  39. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-09-15 09:52 UTCEG score recompute
  41. 2026-09-15 09:52 UTCVendor advisory
  42. 2026-09-15 09:52 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  43. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  44. 2026-09-14 06:35 UTCVendor advisory
  45. 2026-09-14 06:35 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  46. 2026-09-13 18:19 UTCEG score recompute
  47. 2026-09-13 18:19 UTCVendor advisory
  48. 2026-09-13 18:19 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  49. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  50. 2026-09-13 05:58 UTCVendor advisory
  51. 2026-09-13 05:58 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-09-12 17:42 UTCEG score recompute
  53. 2026-09-12 17:42 UTCVendor advisory
  54. 2026-09-12 17:42 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-09-12 05:07 UTCVendor advisory
  56. 2026-09-12 05:07 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-09-11 16:42 UTCEG score recompute
  58. 2026-09-11 16:42 UTCVendor advisory
  59. 2026-09-11 16:42 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  61. 2026-09-11 03:24 UTCVendor advisory
  62. 2026-09-11 03:24 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-09-10 15:06 UTCEG score recompute
  64. 2026-09-10 15:06 UTCVendor advisory
  65. 2026-09-10 15:06 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  66. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  67. 2026-09-09 08:53 UTCEG score recompute
  68. 2026-09-09 08:53 UTCVendor advisory
  69. 2026-09-09 08:53 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  71. 2026-09-07 21:28 UTCEG score recompute
  72. 2026-09-07 21:28 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  74. 2026-09-06 08:29 UTCGHSA enrichmentGHSA-9m96-crvq-5qcj · GitHub severity HIGH · GitHub CVSS 7.8
  75. 2026-09-05 19:27 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-60122?
CVE-2026-60122 is a high-severity vulnerability; its CVE record was published on July 23, 2026. gpsd through release-3.27.5, fixed at commit 4c06658, contains a code injection vulnerability in the gpsprof utility that allows an attacker who controls GPS input data to execute arbitrary OS commands by injecting malicious content into the SKY.satellites[].used field, which is inserted…
When was CVE-2026-60122 made public?
CVE-2026-60122 was made public on July 23, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 23, 2026. EchelonGraph's copy of the record carries a last-modified date of July 30, 2026; the record at its source may have been updated since.
Is CVE-2026-60122 actively exploited?
CVE-2026-60122 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-60122?
CVE-2026-60122 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-60122?
A fix for CVE-2026-60122 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-60122 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-60122

Explore →

Is Your Infrastructure Affected by CVE-2026-60122?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.