# CVE-2026-58302: Path traversal in LinuxCNC

> An unprivileged local user can escalate privileges to root by exploiting path traversal in the SUID rtapi_app binary to load arbitrary shared libraries.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-58302, GHSA-h3vh-9phr-5gjm, UBUNTU-CVE-2026-58302

## What is CVE-2026-58302?

CVE-2026-58302 is a high-severity path traversal vulnerability in LinuxCNC, published on 30 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

rtapi_app in linuxcnc-uspace in LinuxCNC before 2.9.9 allows privilege escalation. It is installed SUID root and loads shared library modules via dlopen() by using a user-supplied module name. Insufficient validation of the module name allows path traversal, enabling an unprivileged local user to load an arbitrary shared library. Because the process retains elevated privileges during module loading, this results in local privilege escalation to root.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

Upgrade to a fixed version.

## Is CVE-2026-58302 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58302 is a high-severity path traversal vulnerability in LinuxCNC, published on 30 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58302 in the wild and no public exploit code.

Affected product: LinuxCNC. 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-58302/ (Markdown: https://insights.sbomify.com/CVE-2026-58302/index.md)
```

## Sources

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

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