Skip to content
major vulnerability· requires attention

Widely used Nexus Repository Manager with unauthenticated RCE and DB access; could disrupt DevOps pipelines and data integrity across industries.

Applications

CVE-2026-5189

9.2
Critical
EPSS 0.46%Patch availableApr 16, 2026

Unauthenticated read/write DB and RCE via hard-coded creds in Nexus Repository Manager.

common questions

Is CVE-2026-5189 being exploited?

Not confirmed. CVE-2026-5189 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.46% probability of exploitation in the next 30 days.

How severe is CVE-2026-5189?

CVE-2026-5189 is rated Critical with a CVSS score of 9.2. 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-5189?

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

What does CVE-2026-5189 affect?

CVE-2026-5189 affects Sonatype Nexus Repository Manager 3.x. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-5189?

Patch to fixed version; rotate credentials; restrict exposure; review binaryListener config

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 3.x
impact

Unauthorized read/write of internal Nexus DB and OS command execution as Nexus process user.

action required

Immediate action required

affected versions
Sonatype Nexus Repository
  • affected>= 3.0.0 and < 3.71.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