CISA ADP Vulnrichment

Answer in brief

CVE-2026-86503 records a Unknown severity vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps JetBrains/IntelliJ IDEA (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 Sep 7, 2026Updated Sep 8, 2026Source checked Sep 8, 2026First seen by HOL Sep 7, 2026Material review Sep 8, 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: Available

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 JetBrains/IntelliJ IDEA (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
JetBrains/IntelliJ IDEAgeneric	>=0 <2026.2.2	2026.2.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for JetBrains/IntelliJ IDEA.
Review the reported fix. Update JetBrains/IntelliJ IDEA to 2026.2.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 7, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 7, 2026

Sources and claim methodology

Source referencejetbrains.com

Upstream source description

In JetBrains IntelliJ IDEA before 2026.2.2 opening an untrusted project could trigger SSRF via Kubernetes spec-source URL fetching

Quoted source text, attributed separately from HOL analysis.