Vulnerability Description
An account holding the nexus:settings:update permission in Nexus Repository 3 (or the equivalent nexus:settings permission in the legacy Nexus Repository 2) could submit arbitrary values as realm identifiers through an internal configuration API that did not validate them against the set of registered realms. Because unrecognized entries were persisted and re-evaluated on every realm load via a legacy code path, this could result in unintended code executing inside the Nexus Repository process, and in some cases a persistent authentication lockout that was not visible through the administrative UI.
Related Weaknesses (CWE)
References
- https://help.sonatype.com/en/sonatype-nexus-repository-3-95-0-release-notes.html
- https://support.sonatype.com/hc/en-us/articles/53849535836179/
FAQ
What is CVE-2026-17593?
CVE-2026-17593 is a documented vulnerability. An account holding the nexus:settings:update permission in Nexus Repository 3 (or the equivalent nexus:settings permission in the legacy Nexus Repository 2) could submit arbitrary values as realm iden...
How severe is CVE-2026-17593?
CVSS scoring is not yet available for CVE-2026-17593. Check NVD for updates.
Is there a patch for CVE-2026-17593?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.