Skip to content
major vulnerability· requires attention

Affects widely-used Nexus Repository Manager; authenticated RCE risk via task management, impacting DevOps pipelines.

Applications

CVE-2026-3199

9.4
Critical
EPSS 0.47%Patch availableApr 9, 2026

Authenticated user can execute arbitrary code via Nexus Repository task management.

common questions

Is CVE-2026-3199 being exploited?

Not confirmed. CVE-2026-3199 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.

How severe is CVE-2026-3199?

CVE-2026-3199 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-3199?

Yes. A fix has been recorded for CVE-2026-3199. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-3199 affect?

CVE-2026-3199 affects Sonatype Nexus Repository Manager (versions 3.22.1–3.90.2). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-3199?

Patch to fixed version; validate task permissions.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Sonatype Nexus Repository Manager (versions 3.22.1–3.90.2)
impact

Code execution by an authorized user via task creation; bypasses nexus.scripts.allowCreation.

action required

Immediate action required

affected versions
Sonatype Nexus Repository
  • affected>= 3.22.1 and < 3.91.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free