How severe is CVE-2026-17593?

CVE-2026-17593 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-17593 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-17593?

CVE-2026-17593 affects Sonatype Nexus Repository Manager. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-17593?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-17593 published?

CVE-2026-17593 was published on 2026-08-07 and last updated on 2026-09-22.

CVE-2026-17593

CVE-2026-17593 is a high-severity vulnerability in Sonatype Nexus Repository Manager with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-470.

Key facts

Severity: High (CVSS 3.x base score 7.2)
CVSS v4: 7.2
EPSS exploit prediction: 1% (54th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-470
Affected product: Sonatype Nexus Repository Manager
Published: 2026-08-07
Last modified: 2026-09-22

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.

Frequently asked questions

What is 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.
How severe is CVE-2026-17593?: CVE-2026-17593 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-17593 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-17593?: CVE-2026-17593 affects Sonatype Nexus Repository Manager. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-17593?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-17593 published?: CVE-2026-17593 was published on 2026-08-07 and last updated on 2026-09-22.

References

Affected products (1)

cpe:2.3:a:sonatype:nexus_repository_manager:*:*:*:*:*:*:*:*

More vulnerabilities in Sonatype Nexus Repository Manager

CVE-2026-5189 — Critical (CVSS 9.8): CWE-798: Use of Hard-coded Credentials in Sonatype Nexus Repository Manager versions 3.0.0 through 3.70.5 allows an…
CVE-2019-9629 — Critical (CVSS 9.8): Sonatype Nexus Repository Manager before 3.17.0 establishes a default administrator user with weak defaults (fixed…
CVE-2019-7238 — Critical (CVSS 9.8): Sonatype Nexus Repository Manager before 3.15.0 has Incorrect Access Control.
CVE-2017-17717 — Critical (CVSS 9.8): Sonatype Nexus Repository Manager through 2.14.5 has weak password encryption with a hardcoded CMMDwoV value in the…
CVE-2026-17603 — High (CVSS 8.8): Nexus Repository 3 did not sufficiently restrict which HikariCP connection-pool properties could be set through the…
CVE-2026-17600 — High (CVSS 8.8): Sonatype Nexus Repository 3 did not immediately terminate a user's active login session or revoke their cached…

All CVEs affecting Sonatype Nexus Repository Manager →

Other CWE-470 (Unsafe Reflection) vulnerabilities

CVE-2026-78030 — Critical (CVSS 9.8): DBI versions before 1.653 for Perl load arbitrary modules via unvalidated dbm_type and dbm_mldbm attributes in…
CVE-2026-93762 — Critical (CVSS 9.8): Mongoid contains an unsafe reflection weakness in the query path used for embedded documents. An application that…
CVE-2026-41871 — Critical (CVSS 9.8): Missing Authorization, Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')…
CVE-2026-40008 — Critical (CVSS 9.8): Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Apache IoTDB. The…
CVE-2026-42027 — Critical (CVSS 9.8): Arbitrary Class Instantiation via Model Manifest in Apache OpenNLP ExtensionLoader Versions Affected: before…
CVE-2025-34393 — Critical (CVSS 9.8): Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, does not correctly verify…

Browse all CWE-470 (Unsafe Reflection) vulnerabilities →