CISA ADP Vulnrichment

Answer in brief

CVE-2024-53920 records a Unknown severity vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps gnu/emacs (generic), n/a/n/a (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Nov 27, 2024Updated Aug 20, 2026Source checked Aug 20, 2026First seen by HOL Aug 20, 2026Material review Aug 20, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps gnu/emacs (generic), n/a/n/a (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
gnu/emacsgeneric	30.0.92	Not reported
n/a/n/ageneric	n/a	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for gnu/emacs, n/a/n/a.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Nov 27, 2024
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 20, 2026

Sources and claim methodology

Upstream source description

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

Quoted source text, attributed separately from HOL analysis.