CVE-2026-17593
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.
What this means for your business
- FIRST's prediction model gives it a 0.3% chance of attack attempts being seen in the next 30 days, ranking above 23% of all known flaws.
What to do
- 1Ask your IT team or provider whether any of your systems use the affected product.
- 2If you do, follow the vendor's guidance. No patch reference has been published yet.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- Not yet scored
- CVSS v4
- 7.2
- Weakness
- CWE-470
- Assigned by
- 103e4ec9-0a87-450b-af77-479448ddef11
Dates
- Published
- 2026-08-07
- Last modified
- 2026-09-01
- Sources
- NVD