Code execution via unsafe Flymake syntax checking
Published Sep 23, 2026 · Updated Sep 23, 2026
Code execution in Flymake in Emacs before 31.2 allows context-dependent attackers to run code by supplying an untrusted source file. Non-Lisp language backends perform syntax checking in a way that executes code embedded in the edited file instead of treating its contents as untrusted. Viewing or editing the file with Flymake and an affected backend enabled runs that code with the privileges of the Emacs user.
Summary
What happened
Code execution in Flymake in Emacs before 31.2 allows context-dependent attackers to run code by supplying an untrusted source file. Non-Lisp language backends perform syntax checking in a way that executes code embedded in the edited file instead of treating its contents as untrusted. Viewing or editing the file with Flymake and an affected backend enabled runs that code with the privileges of the Emacs user.
The record
- CVE
- CVE-2026-96442
- Published
- Sep 23, 2026
- Updated
- Sep 23, 2026
- Vendor
- Commonhaus Foundation
- Product
- Red Hat Enterprise Linux 10
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 23, 2026CVE publishedPublication date reported by the CVE source.
- Sep 23, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started