CVE-2026-17598: Sonatype Nexus Repository 3 did not properly filter internal configuration keys from user-supplied task proper
20
Routine
MEDIUM 4.9UPGRADE
CVE-2026-17598 is a medium-severity flaw (CVSS 4.9) affecting nexus repository manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Sonatype Nexus Repository 3 did not properly filter internal configuration keys from user-supplied task properties when creating or updating a scheduled task through the administrative UI. An account holding permission to create at least one scheduled task type could supply a crafted property value that caused the system to overwrite the configuration of an unrelated, existing task instead of creating a new one.
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Risk facts
| CVSS score | 4.9 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | High |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 87%) |
| CISA exploited list | No |
| Weakness | CWE-915 |
| Published | 2026-08-07 |
| Last modified | 2026-10-23 |
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
sonatype nexus repository manager UPGRADE
Affected: >= 3.91.0 and < 3.95.0
Fixed in: 3.95.0
Safe to downgrade to: a release before 3.91.0
1. Check installed version
apt-cache policy nexus-repository-manager || rpm -q nexus-repository-manager || nexus-repository-manager --version
2. UPGRADE to 3.95.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nexus-repository-manager
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nexus-repository-manager
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.91.0 (Debian / Ubuntu)
apt-cache madison nexus-repository-manager
sudo apt install nexus-repository-manager=<VERSION_BEFORE_3.91.0>
sudo apt-mark hold nexus-repository-manager
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nexus-repository-manager
sudo dnf downgrade nexus-repository-manager-<VERSION_BEFORE_3.91.0>
sudo dnf versionlock add nexus-repository-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Related CVEs
- CVE-2026-17603 HIGH 8.8 UPGRADE Nexus Repository 3 did not sufficiently restrict which HikariCP connection-pool properties could be set throug
- CVE-2026-17600 HIGH 8.8 UPGRADE Sonatype Nexus Repository 3 did not immediately terminate a user's active login session or revoke their cached
- CVE-2026-17599 HIGH 7.2 UPGRADE Nexus Repository 3 contained an endpoint used to change the administrator account password during initial onbo
- CVE-2026-17601 HIGH 7.2 UPGRADE A user holding a permission to update privilege definitions could modify a wildcard privilege already assigned