Nexus Repository 3 - Privilege Escalation

Answer in brief

CVE-2026-14644 records a High severity (CVSS 8.6) vulnerability in Nexus Repository 3 - Privilege Escalation. The current sources do not mark it as known exploited. The current feed maps Sonatype/Nexus Repository 3 (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 Aug 7, 2026Updated Sep 1, 2026Source checked Sep 21, 2026First seen by HOL Aug 7, 2026Material review Sep 1, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.6
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.6. 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 Sonatype/Nexus Repository 3 (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Sonatype/Nexus Repository 3generic	>=3.19.0 <3.95.0	3.95.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for Sonatype/Nexus Repository 3.
Review the reported fix. Update Sonatype/Nexus Repository 3 to 3.95.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

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

Sources and claim methodology

Upstream source description

Nexus Repository 3 contained a privilege escalation vulnerability in the REST privileges API. An authenticated user with permission to manage privileges could, under certain role configurations, escalate their own access to full administrator by exploiting a type-confusion flaw in the privilege update endpoint.

Quoted source text, attributed separately from HOL analysis.