PatchTheCVECVE-2026-17603: Nexus Repository 3 did not sufficiently restrict which HikariCP connection-pool properties could be set throug
41
This month
HIGH 8.8UPGRADE
CVE-2026-17603 is a high-severity flaw (CVSS 8.8) affecting nexus repository manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Nexus Repository 3 did not sufficiently restrict which HikariCP connection-pool properties could be set through the DataStore configuration API. A user holding the nx-datastores-update permission could set the connectionInitSql property to execute arbitrary SQL against the configured database on every new connection. On the default H2 database backend, this could be leveraged to achieve remote code execution as the Nexus process user.
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.8 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.5% (top 59%) |
| CISA exploited list | No |
| Weakness | CWE-94 |
| 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.20.0 and < 3.95.0
Fixed in: 3.95.0
Safe to downgrade to: a release before 3.20.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.20.0 (Debian / Ubuntu)
apt-cache madison nexus-repository-manager
sudo apt install nexus-repository-manager=<VERSION_BEFORE_3.20.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.20.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.
Exact fixes by distribution
Fedora 46 · clementine · FIXED · 1.4.2-1.fc46 · FEDORA-2026-3e748ef4d3 · source
sudo dnf upgrade --advisory=FEDORA-2026-3e748ef4d3
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-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
- CVE-2026-17598 MEDIUM 4.9 UPGRADE Sonatype Nexus Repository 3 did not properly filter internal configuration keys from user-supplied task proper