Nexus Repository 3 - Disabled or Locked Single Sign-On Users Can Sign In Again
Only Nexus Repository 3 Pro versions 3.86.0 through 3.97.x with a SAML or OAuth2/OpenID Connect realm enabled are covered. Fixed in 3.98.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.98.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.98.0.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.1/10CVSS 9.1
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
CVE-2026-113373 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.1 (critical) and affects Nexus Repository 3; fixed in 3.98.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 3.98.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Sonatype Nexus Repository 3 Pro does not check local account status during SAML or OAuth2/OpenID Connect sign-in, so a user whose account was disabled or locked by an administrator can sign in remotely, without logging in first, using valid identity provider credentials for that account. The resulting session carries the account's roles, and the attack needs a named account with valid identity provider credentials.
Read the original description
Sonatype Nexus Repository 3 Pro does not check the local account status when a user signs in through a configured SAML or OAuth2/OpenID Connect identity provider. A user whose account was disabled or locked by an administrator in Nexus Repository can sign in again with valid identity provider credentials for the same account, and then receives a new session with the roles of that account. The attacker needs no Nexus Repository session and no Nexus Repository privilege. The attacker needs a named account that holds valid credentials at the identity provider. The anonymous user is not part of this attack path.
What to do
Upgrade to a fixed version: 3.98.0.
Workaround: Disable the account in your identity provider, or remove it from the groups that map to Nexus Repository roles.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Sonatype Nexus Repository 3
From 3.86.0 · fixed in 3.98.0
Evidence 2
- Advisory
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-113373
Is CVE-2026-113373 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A user whom an administrator disabled or locked in Nexus Repository can sign in again through SAML or OAuth2/OpenID Connect if they still have valid credentials for the same account at the identity provider. The sign-in gives a new session with the roles mapped to that account.Source: support.sonatype.com
Which versions are affected by CVE-2026-113373?
Nexus Repository 3: from 3.86.0 before 3.98.0.Source: cve.now feed data
Am I affected, and how do I check?
Sonatype Nexus Repository 3 Pro versions 3.86.0 up to and including 3.97.x. The bug needs a SAML or OAuth2/OpenID Connect realm enabled, and an account for the user that an administrator has disabled or locked. Check the product version and whether a SAML or OAuth2/OpenID Connect realm is enabled in the settings.Source: support.sonatype.com
How do I fix CVE-2026-113373?
Upgrade Sonatype Nexus Repository 3 Pro to version 3.98.0. Until then, disable the account at the identity provider or remove it from the groups that map to Nexus Repository roles.Source: support.sonatype.com