MEDIUM 4.9

CVE-2026-10741: Nexus Repository Manager Credential Disclosure Vulnerability

Sonatype Nexus Repository Manager versions before 3.93.0 have a flaw that allows repository administrators with delegated authority to access upstream proxy credentials that should be protected. When a Nexus instance is configured to proxy external repositories, it stores credentials needed to authenticate with those upstream servers. An administrator with limited permissions—one who manages only specific repositories—can exploit this vulnerability to retrieve credentials that should remain hidden even from them. This is a credential disclosure issue with medium severity that requires administrator-level access to exploit.

Source data · NVD / CISA · public domain

CVSS
3.1 · 4.9 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Weaknesses (CWE)
CWE-863
Affected products
1 configuration(s)
Published / Modified
2026-06-17 / 2026-07-21

NVD description (verbatim)

Sonatype Nexus Repository Manager before 3.93.0 contains an authorization vulnerability in the proxy repository configuration that allows a delegated repository administrator to disclose stored upstream proxy credentials.

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

The vulnerability exists in the proxy repository configuration logic of Nexus Repository Manager, classified as an authorization bypass affecting credential confidentiality (CWE-863). The flaw permits a delegated repository administrator—a user with restricted administrative privileges—to read stored upstream proxy credentials through the repository configuration interface. The attack requires high privilege level (PR:H) and produces no impact on integrity or availability; the sole risk is confidential disclosure of authentication material. The vulnerability is context-specific to proxy repository setups where upstream authentication is required.

Business impact

Credential disclosure at the administrative level can lead to unauthorized access to upstream repositories or related systems that share credentials. If upstream proxy servers are used to access sensitive artifact sources, compromised credentials could allow an attacker (with initial admin access) to intercept, modify, or exfiltrate supply chain artifacts. Organizations using Nexus for critical software delivery pipelines face risk of lateral movement if those upstream credentials are reused elsewhere. The impact is contained to organizations where delegated repository admins exist and upstream proxy credentials are present.

Affected systems

Sonatype Nexus Repository Manager versions prior to 3.93.0 are affected. Organizations running 3.93.0 or later are not vulnerable. The vulnerability only manifests in instances where proxy repositories with stored upstream credentials are configured; Nexus deployments without proxy repositories or without delegated administrator accounts have reduced exposure.

Exploitability

Exploitation requires existing administrative credentials with delegated repository management authority. No network vulnerability or user interaction is necessary; the attacker must already possess admin-level access to the Nexus instance. This is a privilege escalation within the administrative tier—a delegated admin can see what they are not intended to see. The attack surface is internal and limited to users with admin panel access. There is no known public exploit, and this vulnerability is not tracked in the CISA Known Exploited Vulnerabilities catalog.

Remediation

Upgrade Sonatype Nexus Repository Manager to version 3.93.0 or later. Organizations unable to upgrade immediately should audit proxy repository configurations and restrict delegated administrator roles to the minimum necessary permissions, and consider removing upstream credentials from the Nexus configuration if they can be supplied at request time instead. Review access logs to detect if delegated admins have accessed credential configuration pages.

Patch guidance

Apply the official Sonatype patch by upgrading to Nexus Repository Manager 3.93.0 or a later release. Verify compatibility with your current plugins and configuration before deploying to production. Sonatype provides detailed upgrade instructions and migration notes in their release documentation; consult the vendor advisory for version-specific steps. Plan the upgrade during a maintenance window, as repository access may be briefly interrupted.

Detection guidance

Monitor audit logs for delegated administrators accessing proxy repository configuration, particularly credential fields. Track configuration changes related to upstream proxy credentials. If you maintain HTTP traffic logs, look for unusual access to the Nexus API endpoints related to repository proxy settings (typically under /service/rest/v1/repositories). Search for admin users querying credential storage or performing unauthorized configuration reads. Correlate admin activity with subsequent external connections to upstream repositories.

Why prioritize this

This vulnerability warrants medium priority because it requires high-level privileges to exploit and has no known active exploitation. However, it represents a control failure—delegated admins should not access credentials outside their scope—and could enable further attacks if upstream systems share credentials with other services. Prioritize remediation for Nexus instances in high-trust supply chain roles or where upstream credentials have elevated privilege.

Risk score, explained

CVSS 3.1 score of 4.9 (MEDIUM) reflects the high barrier to exploitation (requires admin access, network-adjacent but not remote unauthenticated) balanced against the severity of credential disclosure. The vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N indicates that while confidentiality impact is high, integrity and availability are unaffected, and the attack requires existing high privileges. This is a moderate risk suitable for standard patching cycles but not emergency response.

Frequently asked questions

Can this vulnerability be exploited over the internet without valid credentials?

No. The vulnerability requires authentication as a delegated repository administrator on the Nexus instance. It is not a remotely unauthenticated attack; the attacker must already have admin-level access to the Nexus web interface.

What upstream systems are at risk if proxy credentials are compromised?

Any upstream repository server (artifact registry, package manager, or Maven Central mirror) whose credentials are stored in Nexus proxy configuration is at risk. If those credentials are reused on other systems, those systems become vulnerable to lateral movement.

Do I need to rotate upstream credentials after patching?

If you suspect a delegated admin may have accessed proxy configuration before you patch, rotating upstream credentials is prudent. After patching to 3.93.0 or later, verify that delegated admins can no longer read upstream credentials, then rotate if the risk window was long.

Does this vulnerability affect Nexus Cloud or only self-hosted instances?

Verify with Sonatype whether Nexus Cloud is affected by this vulnerability, as cloud-hosted instances may have different access controls. Consult the vendor advisory for cloud-specific guidance.

This analysis is provided for informational purposes and reflects the CVE description and CVSS metadata as of the stated modification date. Exploit details and specific attack scenarios are not included. Organizations should verify patch applicability and compatibility with their deployment before applying updates. Consult Sonatype's official security advisory for authoritative guidance on this vulnerability and confirm all version numbers and patch details against the vendor's release notes. This page does not constitute security advice; engage your security team and vendor support for remediation decisions. Source: NVD (public-domain), retrieved 2026-07-27. Analysis generated by SEC.co (claude-haiku-4-5).