Quick answers
- Is CVE-2026-113373 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113373 being exploited in the wild.
- How severe is CVE-2026-113373?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- Sonatype Nexus Repository 3 Pro.
- Is there a fix for CVE-2026-113373?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-113373 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-113373?
- Check whether you run Sonatype Nexus Repository 3 Pro. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
When users authenticate via SAML or OAuth2/OpenID Connect, Nexus Repository 3 Pro does not validate whether the corresponding local account has been disabled or locked by administrators. An attacker with valid identity provider credentials for a named account can obtain a new authenticated session with the original account's roles, bypassing administrative account controls. The attack requires valid credentials at the external identity provider but no pre-existing Nexus session or Nexus-level privilege.
Affected products
- Sonatype Nexus Repository 3 Pro
Timeline
- 2026-11-04: disclosed