CVE-2026-17593
Received Received - Intake

Arbitrary Code Execution in Nexus Repository

Publication date: 2026-08-07

Last updated on: 2026-08-07

Assigner: Sonatype

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-07
Last Modified
2026-08-07
Generated
2026-08-07
AI Q&A
2026-08-07
EPSS Evaluated
N/A
NVD
CVE-2026-17593
EUVD
EUVD-2026-54521

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
sonatype nexus_repository 3.95.0
sonatype nexus_repository From 2.8.0 (inc) to 3.94.x (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-470 The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Sonatype Nexus Repository 3 allows an attacker with the nexus:settings:update permission to submit arbitrary realm identifiers through an internal API. These identifiers are not validated against registered realms and get persisted. When re-evaluated during system restart, they can trigger unintended code execution within the Nexus Repository process. In severe cases, this may cause persistent authentication lockouts that are not visible in the admin UI.

Detection Guidance

Check Nexus Repository version with 'curl -s http://localhost:8081/service/rest/v1/status/check | grep version'. Review realm configurations in the admin UI or via API for unrecognized entries. Look for unexpected authentication lockouts or system behavior changes.

Impact Analysis

An attacker could exploit this to execute arbitrary code within your Nexus Repository, potentially leading to data breaches, system compromise, or denial of service. It may also cause persistent authentication issues that are hard to detect or resolve through normal administrative channels.

Compliance Impact

This vulnerability could lead to unauthorized code execution, potentially exposing sensitive data. This may violate GDPR's data protection requirements or HIPAA's security rules, depending on the data processed by Nexus Repository. Compliance could be impacted if the breach results in unauthorized access to personal or health information.

Mitigation Strategies

Upgrade to Nexus Repository 3.95.0 or later immediately. Restrict nexus:settings:update permission to only trusted roles. Review and remove any unrecognized realm entries from configurations. Monitor for persistent authentication issues.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-17593. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart