BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-53920High confidence

gnu emacs: Improper Control of Generation of Code ('Code Injection')

gnu · emacs

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.60% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs gnu emacs and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceemacsVendor fix publishedDebian records a fixed source-package version for this release.1:30.1+1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceemacsVendor fix publishedDebian records a fixed source-package version for this release.1:28.2+1-15+deb12u4Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceemacsVendor fix publishedDebian records a fixed source-package version for this release.1:30.1+1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceemacsVendor fix publishedDebian records a fixed source-package version for this release.1:30.1+1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsemacsVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1:29.3+1-1ubuntu2+esm3Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivexemacs21Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivexemacs21-packagesUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2024-53920 · CSAF 2.0 · revision 38 · interimSUSE Product Security TeamCVE-2024-53920
191 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • emacs as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • emacs-el as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • emacs-info as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • emacs-nox as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • emacs-x11 as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • etags as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • emacs as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • emacs-el as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • emacs-info as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • emacs-nox as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • emacs-x11 as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • etags as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
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.)
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2024-53920 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityemacs: arbitrary code execution via Lisp macro expansion
16 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • emacs-common as a component of Red Hat Enterprise Linux 10
  • emacs-filesystem as a component of Red Hat Enterprise Linux 10
  • emacs-lucid as a component of Red Hat Enterprise Linux 10
  • emacs-nw as a component of Red Hat Enterprise Linux 10
  • emacs.src as a component of Red Hat Enterprise Linux 10
  • emacs-common as a component of Red Hat Enterprise Linux 6
  • emacs-el as a component of Red Hat Enterprise Linux 6
  • emacs-nox as a component of Red Hat Enterprise Linux 6
  • emacs.src as a component of Red Hat Enterprise Linux 6
  • emacs as a component of Red Hat Enterprise Linux 7
  • emacs-common as a component of Red Hat Enterprise Linux 7
  • emacs-el as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in Emacs. Viewing or editing an untrusted Emacs Lisp source code file can cause arbitrary code execution due to unsafe macro expansion when a user has configured elisp-completion-at-point for code completion or has enabled automatic error checking, such as Flymake or Flycheck.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-52189

No EUVD known-exploited evidence

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.)

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.)

What

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.)

Why

Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.

What

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.)

Why

Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
local access → Improper Control of Generation of Code ('Code Injection') → execute code or commands in the affected security context
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-94 ↗

CWE-94: Improper Control of Generation of Code ('Code Injection'). The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
UnauthenticatedRemote code executionCWE-94Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2024-52189Official EUVD mapping

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.)

Official EUVD record ↗
BSI · German · WID-SEC-2025-1905IBM QRadar SIEM Komponente: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM Komponenten ausnutzen, um Daten zu manipulieren, um einen Denial of Service Angriff durchzuführen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, und um Informationen offenzulegen.

Official advisory ↗
BSI · German · WID-SEC-2024-3558GNU Emacs und Red Hat Enterprise Linux: Schwachstelle ermöglicht Codeausführung

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in GNU Emacs und Red Hat Enterprise Linux ausnutzen, um beliebigen Programmcode auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241204Security Bulletin 04 Dec 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 04 Dec 2024, published on 4 December 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0938Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2024-24786 Référence CVE CVE-2024-44192 https://www.cve.org/CVERecord?id=CVE-2024-44192 Référence CVE CVE-2024-4453 https://www.cve.org/CVERecord?id=CVE-2024-4453 Référence CVE CVE-2024-46951 https://www.cve.org/CVERecord?id=CVE-2024-46951 Référence CVE CVE-2024-46952 https://www.cve.org/CVERecord?id=CVE-2024-46952 Référence CVE CVE-2024-46953 https://www.cve.org/CVERecord?id=CVE-2024-46953 Référence CVE CVE-2024-46954 https://www.cve.org/CVERecord?id=CVE-2024-46954 Référence CVE CVE-2024-46956 https://www.cve.org/CVERecord?id=CVE-2024-46956 Référence CVE CVE-2024-52533 https://www.cve.org/CVERecord?id=CVE-2024-52533 Référence CVE CVE-2024-53920 https://www.cve.org/CVERecord?id=CVE-2024-53920 Référence CVE CVE-2024-55549 https://www.cve.org/CVERecord?id=CVE-2024-55549 Référence CVE CVE-2024-8176 https://www.cve.org/CVERecord?id=CVE-2024-8176 Référence CVE CVE-2025-0913 https://www.cve.org/CVERecord?id=CVE-2025-0913 Référence CVE CVE-2025-11021 https://www.cve.org/CVERecord?id=CVE-2025-11021 Référence CVE CVE-2025-21587 https://www.cve.org/CVERecord?id=CVE-2025-21587 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-24150 https://www.cve.org/CVERecord?id=CVE-2025-24150 Référence CVE CVE-2025-24209 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0746Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-28956 Référence CVE CVE-2024-34397 https://www.cve.org/CVERecord?id=CVE-2024-34397 Référence CVE CVE-2024-43420 https://www.cve.org/CVERecord?id=CVE-2024-43420 Référence CVE CVE-2024-45332 https://www.cve.org/CVERecord?id=CVE-2024-45332 Référence CVE CVE-2024-47535 https://www.cve.org/CVERecord?id=CVE-2024-47535 Référence CVE CVE-2024-50154 https://www.cve.org/CVERecord?id=CVE-2024-50154 Référence CVE CVE-2024-50349 https://www.cve.org/CVERecord?id=CVE-2024-50349 Référence CVE CVE-2024-52006 https://www.cve.org/CVERecord?id=CVE-2024-52006 Référence CVE CVE-2024-52533 https://www.cve.org/CVERecord?id=CVE-2024-52533 Référence CVE CVE-2024-53920 https://www.cve.org/CVERecord?id=CVE-2024-53920 Référence CVE CVE-2024-54661 https://www.cve.org/CVERecord?id=CVE-2024-54661 Référence CVE CVE-2024-57980 https://www.cve.org/CVERecord?id=CVE-2024-57980 Référence CVE CVE-2024-58002 https://www.cve.org/CVERecord?id=CVE-2024-58002 Référence CVE CVE-2024-6531 https://www.cve.org/CVERecord?id=CVE-2024-6531 Référence CVE CVE-2025-1470 https://www.cve.org/CVERecord?id=CVE-2025-1470 Référence CVE CVE-2025-1471 https://www.cve.org/CVERecord?id=CVE-2025-1471 Référence CVE CVE-2025-1494 https://www.cve.org/CVERecord?id=CVE-2025-1494 Référence CVE CVE-2025-1994 https://www.cve.org/CVERecord?id=CVE-2025-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0585Multiples vulnérabilités dans VMware Tanzu

d?id=CVE-2024-38828 Référence CVE CVE-2024-41957 https://www.cve.org/CVERecord?id=CVE-2024-41957 Référence CVE CVE-2024-41965 https://www.cve.org/CVERecord?id=CVE-2024-41965 Référence CVE CVE-2024-43374 https://www.cve.org/CVERecord?id=CVE-2024-43374 Référence CVE CVE-2024-43802 https://www.cve.org/CVERecord?id=CVE-2024-43802 Référence CVE CVE-2024-45306 https://www.cve.org/CVERecord?id=CVE-2024-45306 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-47814 https://www.cve.org/CVERecord?id=CVE-2024-47814 Référence CVE CVE-2024-52615 https://www.cve.org/CVERecord?id=CVE-2024-52615 Référence CVE CVE-2024-53920 https://www.cve.org/CVERecord?id=CVE-2024-53920 Référence CVE CVE-2024-7531 https://www.cve.org/CVERecord?id=CVE-2024-7531 Référence CVE CVE-2025-1215 https://www.cve.org/CVERecord?id=CVE-2025-1215 Référence CVE CVE-2025-22134 https://www.cve.org/CVERecord?id=CVE-2025-22134 Référence CVE CVE-2025-22233 https://www.cve.org/CVERecord?id=CVE-2025-22233 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-24014 https://www.cve.org/CVERecord?id=CVE-2025-24014 Référence CVE CVE-2025-25724 https://www.cve.org/CVERecord?id=CVE-2025-25724 Référence CVE CVE-2025-26603 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0524Multiples vulnérabilités dans VMware Tanzu

ecord?id=CVE-2024-46981 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-49203 https://www.cve.org/CVERecord?id=CVE-2024-49203 Référence CVE CVE-2024-5171 https://www.cve.org/CVERecord?id=CVE-2024-5171 Référence CVE CVE-2024-51741 https://www.cve.org/CVERecord?id=CVE-2024-51741 Référence CVE CVE-2024-51744 https://www.cve.org/CVERecord?id=CVE-2024-51744 Référence CVE CVE-2024-52522 https://www.cve.org/CVERecord?id=CVE-2024-52522 Référence CVE CVE-2024-52616 https://www.cve.org/CVERecord?id=CVE-2024-52616 Référence CVE CVE-2024-53427 https://www.cve.org/CVERecord?id=CVE-2024-53427 Référence CVE CVE-2024-53920 https://www.cve.org/CVERecord?id=CVE-2024-53920 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-55549 https://www.cve.org/CVERecord?id=CVE-2024-55549 Référence CVE CVE-2024-56171 https://www.cve.org/CVERecord?id=CVE-2024-56171 Référence CVE CVE-2024-56378 https://www.cve.org/CVERecord?id=CVE-2024-56378 Référence CVE CVE-2024-56406 https://www.cve.org/CVERecord?id=CVE-2024-56406 Référence CVE CVE-2024-56826 https://www.cve.org/CVERecord?id=CVE-2024-56826 Référence CVE CVE-2024-56827 https://www.cve.org/CVERecord?id=CVE-2024-56827 Référence CVE CVE-2024-6119 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-023085GNU Project の GNU Emacs におけるコードインジェクションの脆弱性

GNU Project の GNU Emacs には、コードインジェクションの脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
n/a: n/a
Fixed
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 27 Nov 2024 · Last source change 21 Sept 2026, 22:07 UTC · CWE-94 · Improper Control of Generation of Code ('Code Injection')

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-52189
Product sourceCISA ADP
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2024-53920.
    Before
    remediation: access.redhat.com/CVE-2024-53920
    After
    no authoritative guidance recorded
    CISA ADP ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    emacs: 30.0.92 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    After
    emacs: 30.0.92 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CISA ADP ↗
  3. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CISA ADP ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    emacs: 30.0.92 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    emacs: 30.0.92 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  6. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2024-53920.
    Before
    remediation: access.redhat.com/CVE-2024-53920
    After
    no authoritative guidance recorded
    CISA ADP ↗
  7. Affected versionsThe structured affected or fixed version information changed.
    Before
    emacs: 30.0.92 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    After
    emacs: 30.0.92 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CISA ADP ↗
  8. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CISA ADP ↗
  9. Affected versionsThe structured affected or fixed version information changed.
    Before
    n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    emacs: 30.0.92 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CISA ADP ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2024-52189↗Vendor CSAF · SUSE Product Security Team↗Red Hat Product Security security advisory↗CISA Vulnrichment SSVC evidence↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-53920 · cve.blacktree.nl