CVE-2026-17593: Nexus Repository - Arbitrary Class Instantiation via Unsafe Realm Configuration
Sonatype · Nexus Repository
Vendor fix available · Affected: Sonatype Nexus Repository · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 56% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Sonatype · Nexus Repositoryfrom 2.8.0 before 3.95.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Sonatype
- Published
- August 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-17593 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.