CVE-2026-17593
Last modified
CVE-2026-17593 is a high-severity vulnerability rated 7.2/10 on the CVSS scale. 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.. EPSS estimates a 0.36% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Sonatype | Nexus Repository Manager | >= 2.8.0, < 3.95.0 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-17593?
How severe is CVE-2026-17593?
How do I fix CVE-2026-17593?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-17586The VK All in One Expansion Unit plugin for WordPress is vul…6.4
- CVE-2026-17587The My Agile Privacy® – CMP, Cookie Consent & Privacy Tools …5.3
- CVE-2026-17589The Shopping Cart & eCommerce Store plugin for WordPress is …4.9
- CVE-2026-1759Improper handling of insufficient permissions or privileges …6.5
- CVE-2026-17590Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2026-17592Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2026-17594Nexus Repository 3 CE/Pro versions 3.0.0 through 3.94.x cont…4.9
- CVE-2026-17595Nexus Repository 3 did not fully sandbox JEXL expressions us…2.7
- CVE-2026-17596Nexus Repository 3 was found to be vulnerable to stored cros…6.1
- CVE-2026-17597Nexus Repository 3 contains a Server-Side Request Forgery (S…2.7
- CVE-2026-17598Sonatype Nexus Repository 3 did not properly filter internal…4.9
- CVE-2026-17599Nexus Repository 3 contained an endpoint used to change the …7.2
Are you affected by CVE-2026-17593?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
