CVE-2026-10748
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 · uneditedAn authenticated user with the nx-licensing-create privilege can upload a specially crafted license file to execute arbitrary operating system commands as the Nexus process user in Sonatype Nexus Repository 3 versions before 3.92.0.
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 confidenceAuthenticated users with nx-licensing-create privilege can upload a malicious license file to achieve arbitrary OS command execution as the Nexus process user in Sonatype Nexus Repository 3 versions prior to 3.92.0. The vulnerability stems from insufficient validation of license file contents during the upload process, allowing command injection.
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:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Nexus Repository 3 versionAccess the Nexus UI: Administration > System > Troubleshooting > View raw log, or check the version banner on the login page. Alternatively, check the 'nexus' service properties or the 'nexus-default.properties' file in the installation directory.Affected if The installed version is 3.x and less than 3.92.0 (e.g., 3.90.0, 3.88.0, 3.85.0, etc.)
-
Verify presence of nx-licensing-create privilegeIn the Nexus UI, go to Administration > Security > Roles and look for a role containing the 'nx-licensing-create' privilege. Then go to Administration > Security > Users to see which users are assigned roles containing this privilege.Affected if Any user account (especially non-administrative or service accounts) is assigned a role that includes the 'nx-licensing-create' privilege.
-
Audit user account trust statusReview the list of users with nx-licensing-create privilege and assess whether each is a trusted administrative user. Check for shared accounts, service accounts, or users with limited physical or MFA security.Affected if The nx-licensing-create privilege is assigned to users who are not fully trusted administrative users, or to users outside the core security team.
-
Check licensing upload functionality accessibilityAttempt to access the license upload interface: Administration > Licensing (or similar path depending on UI version). This feature allows uploading license files.Affected if The license upload interface is accessible to users with the nx-licensing-create privilege, and those users can be authenticated.
You are affected if Nexus Repository 3 version is below 3.92.0 AND any user with the nx-licensing-create privilege is authenticated in the system.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Sonatype Nexus Repository 3 to version 3.92.0 or later. Until then, restrict the nx-licensing-create privilege to only trusted administrators and monitor for unauthorized license uploads.
Sonatype Nexus Repository 3 version 3.92.0
- 1. Verify current Sonatype Nexus Repository 3 version by accessing the application and checking the version in Administration > System > Licensing
- 2. Schedule a maintenance window for the upgrade process
- 3. Create a complete backup of the Nexus data directory (typically $sonatype-work/nexus3) and configuration files
- 4. Download Sonatype Nexus Repository 3 version 3.92.0 or later from the official Sonatype download page
- 5. Stop the Nexus Repository service
- 6. Install the upgrade following Sonatype's official upgrade documentation
- 7. Start the Nexus Repository service
- 8. Verify the upgrade was successful by checking the version in the administration interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10748 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10748 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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