# CVE-2025-1244: Emacs: shell injection vulnerability in gnu emacs via custom "man" uri scheme

> Remote attackers can execute arbitrary shell commands by tricking users into visiting malicious websites or URLs that exploit Emacs' custom man URI scheme.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Feb 2025
- **Updated:** 6 Sep 2026
- **Also known as:** ALSA-2025:1915, ALSA-2025:1917, AZL-56713, AZL-56729, CLSA-2025-1753981054, CLSA-2025-1756317560, DEBIAN-CVE-2025-1244, GHSA-gghq-qp34-gqg8, MGASA-2025-0075, OESA-2025-1165, RHSA-2025:1915, RHSA-2025:1917, RHSA-2025:1961, RHSA-2025:1962, RHSA-2025:1963, RHSA-2025:1964, RHSA-2025:2022, RHSA-2025:2130, RHSA-2025:2157, RHSA-2025:2195, RLSA-2025:1915, RLSA-2025:1917, SUSE-SU-2025:0574-1, SUSE-SU-2025:0589-1, SUSE-SU-2025:0599-1, UBUNTU-CVE-2025-1244, openSUSE-SU-2025:14767-1

## What is CVE-2025-1244?

CVE-2025-1244 is a high-severity command injection vulnerability in Builds for Red Hat OpenShift 1.3.2, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A command injection flaw was found in the text editor Emacs. It could allow a remote, unauthenticated attacker to execute arbitrary shell commands on a vulnerable system. Exploitation is possible by tricking users into visiting a specially crafted website or an HTTP URL with a redirect.

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

## Which versions are affected by CVE-2025-1244?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `emacs` | AlmaLinux:8 | All versions | 1:26.1-13.el8_10 |
| `emacs-common` | AlmaLinux:8 | All versions | 1:26.1-13.el8_10 |
| `emacs-filesystem` | AlmaLinux:8 | All versions | 1:26.1-13.el8_10 |
| `emacs-lucid` | AlmaLinux:8 | All versions | 1:26.1-13.el8_10 |
| `emacs-nox` | AlmaLinux:8 | All versions | 1:26.1-13.el8_10 |
| `emacs-terminal` | AlmaLinux:8 | All versions | 1:26.1-13.el8_10 |
| `emacs` | AlmaLinux:9 | All versions | 1:27.2-11.el9_5.1 |
| `emacs-common` | AlmaLinux:9 | All versions | 1:27.2-11.el9_5.1 |
| `emacs-filesystem` | AlmaLinux:9 | All versions | 1:27.2-11.el9_5.1 |
| `emacs-lucid` | AlmaLinux:9 | All versions | 1:27.2-11.el9_5.1 |
| `emacs-nox` | AlmaLinux:9 | All versions | 1:27.2-11.el9_5.1 |
| `emacs` | Red Hat:enterprise_linux:8::appstream | All versions | 1:26.1-13.el8_10 |
| `emacs-common` | Red Hat:enterprise_linux:8::appstream | All versions | 1:26.1-13.el8_10 |
| `emacs-common-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:26.1-13.el8_10 |
| `emacs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:26.1-13.el8_10 |
| `emacs-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 1:26.1-13.el8_10 |
| `emacs-lucid` | Red Hat:enterprise_linux:8::appstream | All versions | 1:26.1-13.el8_10 |
| `emacs-lucid-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:26.1-13.el8_10 |
| `emacs-nox` | Red Hat:enterprise_linux:8::appstream | All versions | 1:26.1-13.el8_10 |
| `emacs-nox-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:26.1-13.el8_10 |
| `emacs-terminal` | Red Hat:enterprise_linux:8::appstream | All versions | 1:26.1-13.el8_10 |
| `emacs` | Red Hat:enterprise_linux:8::baseos | All versions | 1:26.1-13.el8_10 |
| `emacs-filesystem` | Red Hat:enterprise_linux:8::baseos | All versions | 1:26.1-13.el8_10 |
| `emacs` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-11.el9_5.1 |
| `emacs-common` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-11.el9_5.1 |
| `emacs-common-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-11.el9_5.1 |
| `emacs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-11.el9_5.1 |
| `emacs-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-11.el9_5.1 |
| `emacs-filesystem` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-11.el9_5.1 |
| `emacs-lucid` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-11.el9_5.1 |
| `emacs-lucid-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-11.el9_5.1 |
| `emacs-nox` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-11.el9_5.1 |
| `emacs-nox-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-11.el9_5.1 |
| `emacs` | Red Hat:rhel_aus:8.2::appstream | All versions | 1:26.1-5.el8_2.3 |
| `emacs-common` | Red Hat:rhel_aus:8.2::appstream | All versions | 1:26.1-5.el8_2.3 |
| `emacs-common-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 1:26.1-5.el8_2.3 |
| `emacs-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 1:26.1-5.el8_2.3 |
| `emacs-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 1:26.1-5.el8_2.3 |
| `emacs-lucid` | Red Hat:rhel_aus:8.2::appstream | All versions | 1:26.1-5.el8_2.3 |
| `emacs-lucid-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 1:26.1-5.el8_2.3 |

## How do I fix CVE-2025-1244?

Apply the vendor's patch.

## Is CVE-2025-1244 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1244 and fix it if it is affected.

What it is: CVE-2025-1244 is a high-severity command injection vulnerability in Builds for Red Hat OpenShift 1.3.2, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-1244 in the wild and no public exploit code.

Affected product: Builds for Red Hat OpenShift 1.3.2. 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-2025-1244/ (Markdown: https://insights.sbomify.com/CVE-2025-1244/index.md)
```

## Sources

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

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