RHSA-2025:2157HighCVSS 8.8

Red Hat Security Advisory: emacs security update

Published
March 3, 2025
Last Modified
August 17, 2026

🔗 CVE IDs covered (1)

CVE-2025-1244 →

📋 Description

CVE-2025-1244 — emacs: Shell Injection Vulnerability in GNU Emacs via Custom "man" URI Scheme

🎯 Affected products14

  • Red Hat Enterprise Linux AppStream AUS (v. 8.2)
  • Red Hat Enterprise Linux BaseOS AUS (v. 8.2)
  • emacs-1:26.1-5.el8_2.3.src as a component of Red Hat Enterprise Linux BaseOS AUS (v. 8.2)
  • emacs-1:26.1-5.el8_2.3.x86_64 as a component of Red Hat Enterprise Linux AppStream AUS (v. 8.2)
  • emacs-common-1:26.1-5.el8_2.3.x86_64 as a component of Red Hat Enterprise Linux AppStream AUS (v. 8.2)
  • emacs-common-debuginfo-1:26.1-5.el8_2.3.x86_64 as a component of Red Hat Enterprise Linux AppStream AUS (v. 8.2)
  • emacs-debuginfo-1:26.1-5.el8_2.3.x86_64 as a component of Red Hat Enterprise Linux AppStream AUS (v. 8.2)
  • emacs-debugsource-1:26.1-5.el8_2.3.x86_64 as a component of Red Hat Enterprise Linux AppStream AUS (v. 8.2)
  • emacs-filesystem-1:26.1-5.el8_2.3.noarch as a component of Red Hat Enterprise Linux BaseOS AUS (v. 8.2)
  • emacs-lucid-1:26.1-5.el8_2.3.x86_64 as a component of Red Hat Enterprise Linux AppStream AUS (v. 8.2)
  • emacs-lucid-debuginfo-1:26.1-5.el8_2.3.x86_64 as a component of Red Hat Enterprise Linux AppStream AUS (v. 8.2)
  • emacs-nox-1:26.1-5.el8_2.3.x86_64 as a component of Red Hat Enterprise Linux AppStream AUS (v. 8.2)
  • emacs-nox-debuginfo-1:26.1-5.el8_2.3.x86_64 as a component of Red Hat Enterprise Linux AppStream AUS (v. 8.2)
  • emacs-terminal-1:26.1-5.el8_2.3.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v. 8.2)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: There is no an existing or known mitigation for this issue without disabling part of the Emacs core functionality. However, by avoiding opening or view untrusted files, websites, HTTP URLs or other URI resources with Emacs would reduce or prevent the risk of performing this attack successfully.

🔗 References (4)