CVE-2024-53920

CRITICALNVD 7.89.8▲
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2024-11-27. NVD baseline CVSS 7.8; sources differ by 2.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

In elisp-mode.el in GNU Emacs before 30.1, a user who chooses to invoke elisp-completion-at-point (for code completion) on untrusted Emacs Lisp source code can trigger unsafe Lisp macro expansion that allows attackers to execute arbitrary code. (This unsafe expansion also occurs if a user chooses to enable on-the-fly diagnosis that byte compiles untrusted Emacs Lisp source code.)

CVSS v3
7.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

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 computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

November 27, 2024

Last Modified

September 14, 2026

Advisory Details (5)

Auto-updated Aug 20, 2026
No patch confirmed yet.
generic

Emacs arbitrary code execution and how to avoid it | Hacker News

https://news.ycombinator.com/item?id=42256409
generic

Avoiding arbitrary code execution with macroexpansion - Wilfred Hughes

https://yhetil.org/emacs/CAFXAjY5f4YfHAtZur1RAqH34UbYU56_t6t2Er0YEh1Sb7-W=hg@mail.gmail.com/
generic

Emacs Arbitrary Code Execution and How to Avoid It

https://eshelyaron.com/posts/2024-11-27-emacs-aritrary-code-execution-and-how-to-avoid-it.html
generic

emacs.git - Emacs source repository

https://git.savannah.gnu.org/cgit/emacs.git/tag/?h=emacs-30.0.92
generic

ChangeLog.4 - emacs.git - Emacs source repository

https://git.savannah.gnu.org/cgit/emacs.git/tree/ChangeLog.4

Vendor Advisories for CVE-2024-53920(2)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuemacs-pgtk (1:29.3+1-1ubuntu2+esm3) @ noble2026-09-14ubuntu
redhatdiscovery/discovery-server-rhel9:2.0.0-17525929132025-07-21redhat
redhatemacs-1:26.1-15.el8_102025-07-15redhat
redhatemacs-1:27.2-14.el9_6.22025-06-24redhat
redhatemacs-1:27.2-10.el9_4.22025-05-12redhat
redhatemacs-1:27.2-11.el9_5.22025-05-12redhat
redhatemacs-1:27.2-8.el9_2.32025-05-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
emacs1:27.1+1-3.1 ... 1:27.1+1-3.1+deb11u5 (6 versions)1:27.1+1-3.1+deb11u6—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
emacs1:28.2+1-15, 1:28.2+1-15+deb12u1, 1:28.2+1-15+deb12u2, 1:28.2+1-15+deb12u31:28.2+1-15+deb12u4—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
emacs—1:30.1+1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
emacs—1:30.1+1-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 36× 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.

Showing the most recent 100 of 175 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-53920?
CVE-2024-53920 is a critical vulnerability published on November 27, 2024. In elisp-mode.el in GNU Emacs before 30.1, a user who chooses to invoke elisp-completion-at-point (for code completion) on untrusted Emacs Lisp source code can trigger unsafe Lisp macro expansion that allows attackers to execute arbitrary code. (This unsafe expansion also occurs if a user chooses…
When was CVE-2024-53920 disclosed?
CVE-2024-53920 was first published in the National Vulnerability Database on November 27, 2024, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-53920 actively exploited?
CVE-2024-53920 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.9% of all scored CVEs.
What is the CVSS score of CVE-2024-53920?
CVE-2024-53920 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8.
How do I remediate CVE-2024-53920?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-53920, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-53920

Explore →

Is Your Infrastructure Affected by CVE-2024-53920?

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

Start Free Scan →Browse All CVEs