CVE-2026-17595: Sonatype Nexus Repository 3 · Exposure of Sensitive System Information to an Unauthorized Control Sphere
Affects Sonatype Nexus Repository 3Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.95.0 when convenient.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.95.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade Sonatype Nexus Repository 3 to 3.95.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SonatypeNexus Repository 3 | Affected
| Fixed in
|
Mavencom.sonatype.nexus/nexus-repository-managerpkg:maven/com.sonatype.nexus/nexus-repository-managerOther threats | Affected
| Fixed in– |
CPE configurations (154)
cpe:2.3:a:sonatype:nexus_repository_manager:3.15.0:*:*:*:*:*:*:*cpe:2.3:a:sonatype:nexus_repository_manager:3.15.1:*:*:*:*:*:*:*cpe:2.3:a:sonatype:nexus_repository_manager:3.15.2:*:*:*:*:*:*:*cpe:2.3:a:sonatype:nexus_repository_manager:3.15.3:*:*:*:*:*:*:*cpe:2.3:a:sonatype:nexus_repository_manager:3.16.0:*:*:*:*:*:*:*cpe:2.3:a:sonatype:nexus_repository_manager:3.16.1:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vendor has indicated the issue has been fixed by restricting property access in the JEXL sandbox, but no explicit patch or remediation level is provided in the available data. Users should monitor Sonatype advisories for an official fix and apply it once available. Until then, restrict the nexus:selectors:create permission to trusted users only.
Description
Nexus Repository 3 did not fully sandbox JEXL expressions used in Content Selectors. An account holding the nexus:selectors:create permission could construct an expression that read Java object properties not intended to be exposed to the expression engine, disclosing internal JVM class metadata such as class and classloader names. This issue does not permit method invocation, object construction, or arbitrary code execution. This has been fixed by restricting property access in the JEXL sandbox to the intended data types.