# CVE-2026-79992: Emacs: emacs: command injection via crafted filenames in tramp

> A local attacker can execute arbitrary code in Emacs by tricking a user into processing maliciously crafted filenames via TRAMP.

- **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:** 25 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-98195, CLSA-2026-1792623317, DEBIAN-CVE-2026-79992, GHSA-42vv-cfp2-9qc8, UBUNTU-CVE-2026-79992, openSUSE-SU-2026:11637-1

## What is CVE-2026-79992?

CVE-2026-79992 is a high-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in Emacs TRAMP. A local attacker could exploit this vulnerability by processing maliciously crafted filenames. This occurs because TRAMP concatenates login arguments without proper sanitization, which are then passed to a local shell. Successful exploitation could lead to arbitrary code execution.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `emacs` | openSUSE:Tumbleweed | All versions | 31.1-1.1 |

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

Apply the vendor's patch.

## Is CVE-2026-79992 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79992 is a high-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 25 Aug 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-79992 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-79992/ (Markdown: https://insights.sbomify.com/CVE-2026-79992/index.md)
```

## Sources

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

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