Vulnerability in Sonatype Nexus Repository Manager (CVE-2026-17595)
Summary
Vulnerability in Sonatype Nexus Repository Manager (CVE-2026-17595). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-17595 has been found in Sonatype Nexus Repository Manager.
Risk of unauthorized operations or information disclosure. CVSS score: 2.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Sonatype Nexus Repository Manager CVE-2026-17595" on the vendor's site.
CVE-2026-17595 (Sonatype Nexus Repository Manager) — CWE-497 / CVSS v3 2.7
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-497) exists in Sonatype Nexus Repository Manager.
Check the vendor advisory for the affected versions of Sonatype Nexus Repository Manager.
Severity: Low (CVSS 2.7/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Sonatype Nexus Repository Manager を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch support.sonatype.com
- web help.sonatype.com
- web nvd.nist.gov
- web support.sonatype.com
- web github.com