Arbitrary code execution via unsafe macro expansion
Published Nov 27, 2024 · Updated Aug 20, 2026
Code injection in GNU Emacs before 30.1 allows attackers to execute arbitrary code when a user processes untrusted Emacs Lisp source. In elisp-mode.el, elisp--local-variables and elisp-flymake-byte-compile expand attacker-controlled macros without first treating the file as untrusted. Execution requires a user to invoke code completion or enable on-the-fly diagnostics, although file-local variables can activate Flymake in default configurations.
Summary
What happened
Code injection in GNU Emacs before 30.1 allows attackers to execute arbitrary code when a user processes untrusted Emacs Lisp source. In elisp-mode.el, elisp--local-variables and elisp-flymake-byte-compile expand attacker-controlled macros without first treating the file as untrusted. Execution requires a user to invoke code completion or enable on-the-fly diagnostics, although file-local variables can activate Flymake in default configurations.
The record
- CVE
- CVE-2024-53920
- Published
- Nov 27, 2024
- Updated
- Aug 20, 2026
- Vendor
- The GnuPG Project
- Product
- GNU Emacs
- Classifications
- CWE-94, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 27, 2024CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=30.0.92
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Malicious Emacs Lisp macro-expansion proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo