Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-3199

CRITICAL · 9.4 CVSS v4.0 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
A 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 coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced 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 confidence

A 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.

MitigationUpgrade Sonatype Nexus Repository to version 3.90.3 or later. Verify that the nexus.scripts.allowCreation security control functions correctly after upgrading.

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 checks

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

  1. Identify installed Nexus Repository 3 version
    Navigate to Administration > System > Licensing or check the $NEXUS_HOME/sonatype-work/nexus3/installed.json file for the version number
    Affected if The installed version falls within 3.22.1 through 3.90.2 inclusive
  2. Verify task creation permission configuration
    Navigate 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 permissions
    Affected if Any authenticated user or role has task creation (NX TASK CREATE) permissions enabled
  3. Check the nexus.scripts.allowCreation setting
    Locate 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 configuration
    Affected 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.

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 to version 3.90.3 or later. Verify that the nexus.scripts.allowCreation security control functions correctly after upgrading.

Recommended fix Moderate confidence

Nexus Repository 3.91.0 or later

  1. Identify current Nexus Repository 3 version by navigating to Administration > System > Capabilities or checking the footer of any Nexus page
  2. Backup the Nexus data directory (typically <install-dir>/sonatype-work/nexus3) and configuration files
  3. Stop the Nexus Repository service
  4. Download Nexus Repository 3.91.0 or later from https://help.sonatype.com/display/NXRM3/Download+Archives
  5. Install the new version following standard upgrade procedures at https://help.sonatype.com/display/NXRM3/Upgrading
  6. Start the Nexus Repository service
  7. Verify the upgrade by logging in and checking the version in Administration > System > Information
  8. Review task configurations to ensure no unauthorized tasks were created during any potential exploitation
Caveat Review release notes for breaking changes between 3.90.2 and 3.91.0; some plugin or integration compatibility may be affected

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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 locally
dbcve dependency scanner

Check 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3199 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