Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-17593: An account holding the nexus:settings:update permission in Nexus Repository 3 (or the equivalent nexus:setting

39
Routine
HIGH 7.2UPGRADE

CVE-2026-17593 is a high-severity flaw (CVSS 7.2) affecting nexus repository manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 co

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance0.8% (top 45%)
CISA exploited listNo
WeaknessCWE-470
Published2026-08-07
Last modified2026-09-22
Publisher (CNA): Sonatype · Vendor: sonatype

Share: LinkedIn · X · Reddit

Last updated 2026-09-22 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

sonatype nexus repository manager UPGRADE
Affected: >= 2.8.0 and < 3.95.0
Fixed in: 3.95.0
Safe to downgrade to: a release before 2.8.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 2.8.0 (Debian / Ubuntu)
apt-cache madison nexus-repository-manager sudo apt install nexus-repository-manager=<VERSION_BEFORE_2.8.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_2.8.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.

Quick answers

How do I fix CVE-2026-17593?

nexus repository manager: upgrade to 3.95.0. Exact commands for each OS are on this page.

Is CVE-2026-17593 being exploited?

CVE-2026-17593 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-17593 affect?

CVE-2026-17593 affects nexus repository manager. Severity is high (CVSS 7.2). 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 configuratio

How urgent is CVE-2026-17593?

Priority 39/100. High severity

Software pages

Sonatype Nexus vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.