# CVE-2026-108976: Command injection in Emacs

> Attackers can execute arbitrary OS commands via crafted filenames in GNU Emacs TRAMP due to incomplete input validation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-107949, GHSA-f2f9-wp9v-23mf, OESA-2026-4648, OESA-2026-4649, OESA-2026-4650, UBUNTU-CVE-2026-108976

## What is CVE-2026-108976?

CVE-2026-108976 is a high-severity command injection vulnerability in GNU Emacs, published on 11 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

GNU Emacs before 31.2 (and TRAMP through 2.8.2) allows OS command injection via a filename because tramp-user-regexp has an incomplete list of disallowed inputs. NOTE: this issue exists because of an incomplete fix for CVE-2026-79992.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

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


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

Apply the vendor's patch.

## Is CVE-2026-108976 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108976 is a high-severity command injection vulnerability in GNU Emacs, published on 11 Oct 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-108976 in the wild and no public exploit code.

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

## Sources

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

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