CVE-2026-96269

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-84868 (ENISA EUVD) · GHSA-29x7-3q83-3x3v (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 22, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Sep 22, 2026
Patch available.
Web page

#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#227
Web page

bug#80574: 31.0.50; `intern` should not depend on the current-buffer

https://yhetil.org/emacs/jwvtsph1aoj.fsf-monnier+emacs@gnu.org/T/#m319545e835fb71d764bf868166632d4633167a75

Vendor Advisories for CVE-2026-96269(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
emacs1:28.2+1-15 ... 1:30.2+1-9 (53 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
emacs1:30.1+1-6
  • every version up to 1:30.1+1-6+deb13u1: fixed in 1:30.1+1-6+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
emacs1:30.1+1-6 ... 1:30.2+1-9 (14 versions)
  • every version up to 1:30.2+1-11: fixed in 1:30.2+1-11
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 83× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 146 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 46 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-27 12:44 UTCEG score recompute
  8. 2026-10-27 12:44 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  9. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-25 13:48 UTCEG score recompute
  12. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-19 14:39 UTCEG score recompute
  19. 2026-10-19 14:39 UTCVendor advisory
  20. 2026-10-19 14:38 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  21. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-18 02:57 UTCEG score recompute
  23. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 75 more
  1. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-13 04:09 UTCEG score recompute
  4. 2026-10-13 04:09 UTCVendor advisory
  5. 2026-10-13 04:09 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  6. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-12 14:40 UTCEG score recompute
  8. 2026-10-12 01:37 UTCVendor advisory
  9. 2026-10-12 01:37 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  10. 2026-10-11 19:11 UTCEG score recompute
  11. 2026-10-11 16:27 UTCEG score recompute
  12. 2026-10-11 13:39 UTCEG score recompute
  13. 2026-10-11 11:08 UTCVendor advisory
  14. 2026-10-11 11:08 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  15. 2026-10-10 21:54 UTCEG score recompute
  16. 2026-10-10 21:54 UTCVendor advisory
  17. 2026-10-10 21:54 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  18. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-10 08:44 UTCEG score recompute
  20. 2026-10-10 08:44 UTCVendor advisory
  21. 2026-10-10 08:43 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  22. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-09 19:32 UTCVendor advisory
  24. 2026-10-09 19:32 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  25. 2026-10-09 06:22 UTCEG score recompute
  26. 2026-10-09 06:22 UTCVendor advisory
  27. 2026-10-09 06:22 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  28. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  29. 2026-10-08 17:11 UTCVendor advisory
  30. 2026-10-08 17:11 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  31. 2026-10-08 02:12 UTCEG score recompute
  32. 2026-10-08 02:12 UTCVendor advisory
  33. 2026-10-08 02:12 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  34. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  35. 2026-10-07 13:00 UTCVendor advisory
  36. 2026-10-07 13:00 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  37. 2026-10-06 23:49 UTCEG score recompute
  38. 2026-10-06 23:49 UTCVendor advisory
  39. 2026-10-06 23:49 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  40. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  41. 2026-10-06 10:39 UTCVendor advisory
  42. 2026-10-06 10:38 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  43. 2026-10-05 21:21 UTCEG score recompute
  44. 2026-10-05 21:21 UTCVendor advisory
  45. 2026-10-05 21:21 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  46. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-10-05 07:57 UTCEG score recompute
  48. 2026-10-05 07:57 UTCVendor advisory
  49. 2026-10-05 07:57 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  50. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  51. 2026-10-04 18:46 UTCVendor advisory
  52. 2026-10-04 18:46 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  53. 2026-10-04 05:26 UTCVendor advisory
  54. 2026-10-04 05:26 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  55. 2026-10-03 16:15 UTCEG score recompute
  56. 2026-10-03 16:15 UTCVendor advisory
  57. 2026-10-03 16:15 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  58. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  59. 2026-10-03 03:05 UTCEG score recompute
  60. 2026-10-03 03:05 UTCVendor advisory
  61. 2026-10-03 03:05 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  62. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  63. 2026-10-02 13:54 UTCVendor advisory
  64. 2026-10-02 13:54 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  65. 2026-10-02 00:44 UTCEG score recompute
  66. 2026-10-02 00:44 UTCVendor advisory
  67. 2026-10-02 00:44 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  68. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  69. 2026-10-01 11:29 UTCVendor advisory
  70. 2026-10-01 11:29 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  71. 2026-09-30 22:18 UTCEG score recompute
  72. 2026-09-30 22:18 UTCVendor advisory
  73. 2026-09-30 22:18 UTCGHSA enrichmentGHSA-29x7-3q83-3x3v · GitHub severity HIGH
  74. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  75. 2026-09-30 09:08 UTCVendor advisory

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-96269?
CVE-2026-96269 is a high-severity vulnerability; its CVE record was published on September 22, 2026. 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.
When was the CVE record for CVE-2026-96269 published?
The CVE record for CVE-2026-96269 was published on September 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-96269 actively exploited?
CVE-2026-96269 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96269?
CVE-2026-96269 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-96269?
A fix for CVE-2026-96269 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-96269 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-96269

Explore →

Is Your Infrastructure Affected by CVE-2026-96269?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs