dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-10741

MEDIUM · 5.9 CVSS v4.0 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Sonatype Nexus Repository Manager before version 3.93.0 has an authorization flaw in the proxy repository configuration that permits a delegated repository administrator to access and disclose upstream proxy credentials that should be restricted from their view.

MitigationUpgrade Sonatype Nexus Repository Manager to version 3.93.0 or later to remediate the authorization bypass. Review existing delegated administrator permissions and rotate any exposed credentials as a precaution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Nexus Repository Manager version
    Access the Nexus administration interface and navigate to System > Information, or check the version from the bundled support zip or startup logs. Compare the installed version against the 3.93.0 threshold.
    Affected if The installed version is any release before 3.93.0 (e.g., 3.92.0, 3.90.0, etc.)
  2. Verify delegated administrator exists
    In the Nexus administration interface, navigate to Administration > Security > Roles and Users. Identify if any users or roles are assigned the 'nx-repository-admin' or similar delegated administrator role with repository-level permissions.
    Affected if Delegated repository administrator users or roles are configured with permissions to manage repositories.
  3. Locate proxy repositories with upstream credentials
    Navigate to Administration > Repository > Repositories. Review all proxy repository configurations (type: proxy) and check if any have HTTP or repository URL credentials stored in the authentication fields.
    Affected if Proxy repositories exist that store upstream HTTP authentication credentials (username/password or anonymous settings).
  4. Verify credential visibility for delegated admins
    As a delegated repository administrator user (not a full administrator), attempt to view the configuration of a proxy repository that contains upstream credentials. Observe whether the credential fields are visible or accessible in the delegated admin interface.
    Affected if A delegated repository administrator can view or export the upstream proxy credentials in the repository configuration.

You are affected if running Nexus Repository Manager version 3.x before 3.93.0 with delegated administrators who can access proxy repositories configured with upstream authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Sonatype Nexus Repository Manager to version 3.93.0 or later to remediate the authorization bypass. Review existing delegated administrator permissions and rotate any exposed credentials as a precaution.

Recommended fix Moderate confidence

Nexus Repository Manager 3.93.0

  1. 1. Back up your current Nexus Repository Manager configuration and data
  2. 2. Download Nexus Repository Manager version 3.93.0 or later from the official Sonatype download page
  3. 3. Stop the currently running Nexus Repository Manager service
  4. 4. Install the new version following the standard upgrade procedure for your deployment method
  5. 5. Start the upgraded Nexus Repository Manager service
  6. 6. Verify that the proxy repository configuration authorization issue is resolved by testing that delegated repository administrators can no longer access upstream proxy credentials
Caveat Review the 3.93.0 release notes for any breaking changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10741 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10741 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data