CVE-2026-17593: Nexus Repository - Arbitrary Class Instantiation via Unsafe Realm Configuration
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-17593?
CVE-2026-17593 has a risk rating of 54, indicating a medium severity vulnerability.
How do I fix CVE-2026-17593?
To fix CVE-2026-17593, ensure that only validated realm identifiers are accepted through the internal configuration API.
What software is affected by CVE-2026-17593?
CVE-2026-17593 affects Sonatype Nexus Repository 3 and the legacy Nexus Repository 2.
Who is at risk from CVE-2026-17593?
Accounts with the nexus:settings:update permission in Nexus Repository 3 or the equivalent nexus:settings permission in Nexus Repository 2 are at risk from CVE-2026-17593.
What type of vulnerability is CVE-2026-17593?
CVE-2026-17593 is an arbitrary class instantiation vulnerability due to unsafe realm configuration.