CVE-2026-17593: high-severity vulnerability in Sonatype Nexus Repository
Nexus Repository - Arbitrary Class Instantiation via Unsafe Realm Configuration
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.2epss 0.8%
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
Affected products
Sonatype · Nexus RepositoryRelated CVEs — Sonatype Nexus Repository
In the same product, most dangerous first.
CVE-2024-4956HIGHNexus Repository 3 - Path TraversalEPSS 19.2%CVE-2024-5082HIGHNexus Repository 2 - Remote Code ExecutionEPSS 3.1%CVE-2026-3199CRITICALNexus Repository 3 - Authenticated Remote Code Execution via Task Property InjectionEPSS 0.6%CVE-2026-5189CRITICALNexus Repository 3 - Hardcoded Credential in Internal Database ComponentEPSS 0.5%CVE-2025-9868HIGHNexus Repository 2 - SSRF Vulnerability in Remote Browser PluginEPSS 0.5%CVE-2026-0601MEDIUMNexus Repository 3 - Cross-Site ScriptingEPSS 0.4%