# CVE-2026-60122: gpsd gpsprof Code Injection via SKY.satellites used Field

> An attacker controlling GPS input can execute arbitrary OS commands via unsanitized data in gpsprof's gnuplot script generation.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** ALSA-2026:65162, ALSA-2026:65606, CLSA-2026-1789034846, CLSA-2026-1789389842, DEBIAN-CVE-2026-60122, GHSA-9m96-crvq-5qcj, MGASA-2026-0509, RHSA-2026:65162, RHSA-2026:65606, RLSA-2026:65162, RLSA-2026:65606, UBUNTU-CVE-2026-60122, openSUSE-SU-2026:11891-1

## What is CVE-2026-60122?

CVE-2026-60122 is a high-severity code injection vulnerability in gpsd, published on 23 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-60122?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gpsd` | AlmaLinux:10 | All versions | 1:3.26.1-3.el10_2.2 |
| `gpsd-clients` | AlmaLinux:10 | All versions | 1:3.26.1-3.el10_2.2 |
| `python3-gpsd` | AlmaLinux:10 | All versions | 1:3.26.1-3.el10_2.2 |
| `gpsd-minimal` | AlmaLinux:9 | All versions | 1:3.26.1-2.el9_8.2 |
| `gpsd-minimal-clients` | AlmaLinux:9 | All versions | 1:3.26.1-2.el9_8.2 |
| `gpsd` | Red Hat:enterprise_linux:10.2 | All versions | 1:3.26.1-3.el10_2.2 |
| `gpsd-clients` | Red Hat:enterprise_linux:10.2 | All versions | 1:3.26.1-3.el10_2.2 |
| `gpsd-clients-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 1:3.26.1-3.el10_2.2 |
| `gpsd-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 1:3.26.1-3.el10_2.2 |
| `gpsd-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 1:3.26.1-3.el10_2.2 |
| `python3-gpsd` | Red Hat:enterprise_linux:10.2 | All versions | 1:3.26.1-3.el10_2.2 |
| `python3-gpsd-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 1:3.26.1-3.el10_2.2 |
| `gpsd-minimal` | Red Hat:enterprise_linux:9::appstream | All versions | 1:3.26.1-2.el9_8.2 |
| `gpsd-minimal-clients` | Red Hat:enterprise_linux:9::appstream | All versions | 1:3.26.1-2.el9_8.2 |
| `gpsd-minimal-clients-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:3.26.1-2.el9_8.2 |
| `gpsd-minimal-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:3.26.1-2.el9_8.2 |
| `gpsd-minimal-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 1:3.26.1-2.el9_8.2 |
| `gpsd` | Rocky Linux:10 | All versions | 1:3.26.1-3.el10_2.2 |
| `gpsd-minimal` | Rocky Linux:9 | All versions | 1:3.26.1-2.el9_8.2 |
| `gpsd` | openSUSE:Tumbleweed | All versions | 3.27.5-4.1 |

## How do I fix CVE-2026-60122?

Apply the vendor's patch.

## Is CVE-2026-60122 being exploited?

There is no known exploitation of CVE-2026-60122 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-60122 and fix it if it is affected.

What it is: CVE-2026-60122 is a high-severity code injection vulnerability in gpsd, published on 23 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-60122 in the wild and no public exploit code.

Affected product: gpsd. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-60122/ (Markdown: https://insights.sbomify.com/CVE-2026-60122/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-60122
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-60122
- OSV: https://osv.dev/vulnerability/CVE-2026-60122

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-60122/
Summaries are generated and may contain mistakes; the official description above is the record.