# CVE-2026-97712: Nexus Repository 3 - Privilege Escalation via Role Management

> Users with role management permissions can escalate privileges to full administrative access by granting themselves unauthorized roles.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-3mxp-fmm4-39rw

## What is CVE-2026-97712?

CVE-2026-97712 is a high-severity vulnerability in Sonatype Nexus Repository 3, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sonatype Nexus Repository 3 allows a user that holds the role create or role update permission to grant roles and privileges that the account does not hold. This can give the user more access than intended, up to full administrative access.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-97712?


## How do I fix CVE-2026-97712?

No fix has been published for CVE-2026-97712 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-97712 being exploited?

There is no known exploitation of CVE-2026-97712 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97712 and fix it if it is affected.

What it is: CVE-2026-97712 is a high-severity vulnerability in Sonatype Nexus Repository 3, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97712 in the wild and no public exploit code.

Affected product: Sonatype Nexus Repository 3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97712/ (Markdown: https://insights.sbomify.com/CVE-2026-97712/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97712
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97712
- OSV: https://osv.dev/vulnerability/CVE-2026-97712

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97712/
Summaries are generated and may contain mistakes; the official description above is the record.