CISA ADP Vulnrichment

Answer in brief

CVE-2026-24332 records a Unknown severity vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps Discord/WebSocket API service (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 Jan 22, 2026Updated Sep 12, 2026Source checked Sep 13, 2026First seen by HOL Sep 12, 2026Material review Sep 12, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
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 Discord/WebSocket API service (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Discord/WebSocket API servicegeneric	0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Discord/WebSocket API service.
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
Jan 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 12, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 12, 2026

Sources and claim methodology

Source referencexmrcat.org

Upstream source description

Discord through 2026-01-16 allows gathering information about whether a user's client state is Invisible (and not actually offline) because the response to a WebSocket API request includes the user in the presences array (with "status": "offline"), whereas offline users are omitted from the presences array. This is arguably inconsistent with the UI description of Invisible as "You will appear offline." NOTE: a third-party report suggests that this was remediated later in 2026.

Quoted source text, attributed separately from HOL analysis.