CVE-2026-3199
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 · uneditedA vulnerability in the task management component of Sonatype Nexus Repository versions 3.22.1 through 3.90.2 allows an authenticated attacker with task creation permissions to execute arbitrary code, bypassing the nexus.scripts.allowCreation security control.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 confidenceA critical vulnerability in the task management component of Sonatype Nexus Repository 3 allows authenticated users with task creation permissions to execute arbitrary code. The flaw bypasses the nexus.scripts.allowCreation security control, enabling script execution despite that protection being in place.
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
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L/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 versionNavigate to Administration > System > Licensing or check the $NEXUS_HOME/sonatype-work/nexus3/installed.json file for the version numberAffected if The installed version falls within 3.22.1 through 3.90.2 inclusive
-
Verify task creation permission configurationNavigate to Administration > Security > Roles and examine which roles have the 'NX TASK CREATE' privilege assigned, or check Administration > Security > Users to see which users have direct task creation permissionsAffected if Any authenticated user or role has task creation (NX TASK CREATE) permissions enabled
-
Check the nexus.scripts.allowCreation settingLocate the nexus.properties file (typically in $NEXUS_HOME/sonatype-work/nexus3/etc/nexus.properties) or access the API at /service/rest/v1/capabilities to verify the current value of the nexus.scripts.allowCreation configurationAffected if The nexus.scripts.allowCreation setting exists and is set to true, or the setting does not exist at all (default behavior)
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 to version 3.90.3 or later. Verify that the nexus.scripts.allowCreation security control functions correctly after upgrading.
Nexus Repository 3.91.0 or later
- Identify current Nexus Repository 3 version by navigating to Administration > System > Capabilities or checking the footer of any Nexus page
- Backup the Nexus data directory (typically <install-dir>/sonatype-work/nexus3) and configuration files
- Stop the Nexus Repository service
- Download Nexus Repository 3.91.0 or later from https://help.sonatype.com/display/NXRM3/Download+Archives
- Install the new version following standard upgrade procedures at https://help.sonatype.com/display/NXRM3/Upgrading
- Start the Nexus Repository service
- Verify the upgrade by logging in and checking the version in Administration > System > Information
- Review task configurations to ensure no unauthorized tasks were created during any potential exploitation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3199 — 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-3199 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