GNU Emacs 28.1 through 31.1 allows arbitrary code execution upon opening a file, because an untrusted value of read-symbol-shorthands affects the intern and unintern functions. This affects the default configuration; no particular user settings are required to trigger it.
CVE-2026-96269
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 24, 2026
Advisory Details (2)
Auto-updated Sep 22, 2026#80574 - 31.0.50; `intern` should not depend on the current-buffer - GNU bug report logs
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=80574#227bug#80574: 31.0.50; `intern` should not depend on the current-buffer
https://yhetil.org/emacs/[email protected]/T/#m319545e835fb71d764bf868166632d4633167a75Vendor Advisories for CVE-2026-96269(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 02:23 UTCEG score recompute
- 2026-09-24 02:23 UTCGHSA enrichment
- 2026-09-24 01:57 UTCEG score recompute
- 2026-09-24 01:57 UTCGHSA enrichment
- 2026-09-23 23:55 UTCEG score recompute
- 2026-09-23 23:55 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 10:45 UTCGHSA enrichment
- 2026-09-22 21:33 UTCEG score recompute
- 2026-09-22 21:33 UTCGHSA enrichment
- 2026-09-22 20:43 UTCEG score recompute
- 2026-09-22 20:42 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-829
Frequently asked(5)
What is CVE-2026-96269?
When was CVE-2026-96269 disclosed?
Is CVE-2026-96269 actively exploited?
What is the CVSS score of CVE-2026-96269?
How do I remediate CVE-2026-96269?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-96269
Is Your Infrastructure Affected by CVE-2026-96269?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.