Missing authorization in Nexus Repository 3 NuGet symbol package upload
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-862.
Summary
Sonatype Nexus Repository 3 from 3.95.0 before 3.97.0 has a missing authorization check in the NuGet Components API upload path. An account with only repository read and browse privileges can upload and store NuGet symbol packages (.snupkg) in a hosted repository, bypassing the write-permission check (CWE-862). Exploitation requires a hosted NuGet repository with Symbol Server enabled, and it can also be met without an account if anonymous access is enabled, because the anonymous user holds read and browse privileges by default.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Description from the CNA
A missing authorization check in Nexus Repository 3's NuGet Components API upload path allows an account holding only repository read and browse privileges to upload and persist NuGet symbol packages (.snupkg) to a hosted repository, bypassing the write-permission check enforced for ordinary package uploads. Exploitation requires a hosted NuGet repository with Symbol Server enabled. If anonymous access is enabled, the built-in anonymous user holds read and browse privileges across all repositories by default, so this precondition can also be met without an authenticated account.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Sonatype | Nexus Repository 3 | 3.95.0 to before 3.97.0 | 3.97.0 | Patch available | CNA |
- Nexus Repository 3 VendorSonatype Affected 3.95.0 to before 3.97.0 Fixed in 3.97.0 Patch available CNA
CPE names CNA · 9
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:sonatype:nexus_repository_manager:3.95.0:*:*:*:*:*:*:* | 3.95.0 | — | Sonatype |
| cpe:2.3:a:sonatype:nexus_repository_manager:3.95.1:*:*:*:*:*:*:* | 3.95.1 | — | Sonatype |
| cpe:2.3:a:sonatype:nexus_repository_manager:3.95.2:*:*:*:*:*:*:* | 3.95.2 | — | Sonatype |
| cpe:2.3:a:sonatype:nexus_repository_manager:3.95.3:*:*:*:*:*:*:* | 3.95.3 | — | Sonatype |
| cpe:2.3:a:sonatype:nexus_repository_manager:3.95.4:*:*:*:*:*:*:* | 3.95.4 | — | Sonatype |
| cpe:2.3:a:sonatype:nexus_repository_manager:3.96.0:*:*:*:*:*:*:* | 3.96.0 | — | Sonatype |
| cpe:2.3:a:sonatype:nexus_repository_manager:3.96.1:*:*:*:*:*:*:* | 3.96.1 | — | Sonatype |
| cpe:2.3:a:sonatype:nexus_repository_manager:3.96.2:*:*:*:*:*:*:* | 3.96.2 | — | Sonatype |
| cpe:2.3:a:sonatype:nexus_repository_manager:3.96.3:*:*:*:*:*:*:* | 3.96.3 | — | Sonatype |
- cpe:2.3:a:sonatype:nexus_repository_manager:3.95.0:*:*:*:*:*:*:* Versions 3.95.0 — ·Sonatype
- cpe:2.3:a:sonatype:nexus_repository_manager:3.95.1:*:*:*:*:*:*:* Versions 3.95.1 — ·Sonatype
- cpe:2.3:a:sonatype:nexus_repository_manager:3.95.2:*:*:*:*:*:*:* Versions 3.95.2 — ·Sonatype
- cpe:2.3:a:sonatype:nexus_repository_manager:3.95.3:*:*:*:*:*:*:* Versions 3.95.3 — ·Sonatype
- cpe:2.3:a:sonatype:nexus_repository_manager:3.95.4:*:*:*:*:*:*:* Versions 3.95.4 — ·Sonatype
- cpe:2.3:a:sonatype:nexus_repository_manager:3.96.0:*:*:*:*:*:*:* Versions 3.96.0 — ·Sonatype
- cpe:2.3:a:sonatype:nexus_repository_manager:3.96.1:*:*:*:*:*:*:* Versions 3.96.1 — ·Sonatype
- cpe:2.3:a:sonatype:nexus_repository_manager:3.96.2:*:*:*:*:*:*:* Versions 3.96.2 — ·Sonatype
- cpe:2.3:a:sonatype:nexus_repository_manager:3.96.3:*:*:*:*:*:*:* Versions 3.96.3 — ·Sonatype
Remediation
Upgrade Sonatype Nexus Repository 3 to version 3.97.0 or later, which fixes the issue.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
- Fix · CNA Nexus Repository 3 (Sonatype) Fixed in 3.97.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Sonatype Nexus Repository 3 3.97.0
4 records Highest priority Priority LOW 4 LOW
Other records, highest priority first
- TI-2026-74835 Sonatype Nexus Repository 3 lets users escalate privileges via rolesPriority LOW 39
- TI-2026-74833 Unsafe reflection in Sonatype Nexus Repository 3 ExtDirect endpointPriority LOW 37
- TI-2026-74834 Stored cross-site scripting in Sonatype Nexus Repository 3 Browse UIPriority LOW 23
Timeline
- 2026-10-16 Threatist record created from CVE-2026-97665
References
More Sonatype vulnerabilities
- TI-2019-05133 Sonatype Nexus Repository Manager before 3.15.0 has Incorrect Access Control. KEVCVSS 3.1CRITICAL 9.8
- TI-2020-08218 Sonatype Nexus Repository before 3.21.2 allows JavaEL Injection (issue 1 of 2). KEVCVSS 3.1HIGH 8.8
- TI-2020-08220 Sonatype Nexus Repository before 3.21.2 allows Remote Code Execution. CVSS 3.1HIGH 7.2
- TI-2024-04604 Nexus Repository 3 - Path Traversal CVSS 3.1HIGH 7.5
- TI-2019-03883 OS command injection in Nexus Repository Manager CVSS 3.0HIGH 8.8
- TI-2026-02763 Nexus Repository 3 - Authenticated Remote Code Execution via Task Property Injection CVSS 4.0CRITICAL 9.4
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences