dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2026-5189

CRITICAL · 9.2 CVSS v4.0 Published 2026-04-15
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 No privileges 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
CWE-798: Use of Hard-coded Credentials in Sonatype Nexus Repository Manager versions 3.0.0 through 3.70.5 allows an unauthenticated attacker with network access to gain unauthorized read/write access to the internal database and execute arbitrary OS commands as the Nexus process user. Exploitation requires the non-default nexus.orient.binaryListenerEnabled=true configuration to be enabled.

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 · moderate confidence

Hardcoded credentials in Sonatype Nexus Repository Manager 3.0.0-3.70.5 allow unauthenticated remote attackers to gain database access and execute OS commands as the Nexus process user, but only when the non-default nexus.orient.binaryListenerEnabled=true setting is enabled.

MitigationDisable the nexus.orient.binaryListenerEnabled setting if enabled, and upgrade to a patched version once available from Sonatype.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/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 checks

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

  1. Identify if Sonatype Nexus Repository Manager 3 is installed
    Look for the Nexus installation directory, typically under /opt/nexus, /usr/local/nexus, or C:\Program Files\sonatype\nexus on Windows. Check for the 'nexus' service running on the system.
    Affected if The software is present and running
  2. Determine the installed Nexus 3 version
    Check the version file in the installation, commonly found at <nexus-home>/sonatype-work/nexus3/version.txt, or access the Nexus UI and view the About page. Compare the version number to the affected range 3.0.0 through 3.70.5.
    Affected if The version falls within 3.0.0 to 3.70.5 inclusive
  3. Check if the vulnerable OrientDB listener setting is enabled
    Locate the nexus.properties file, typically in <nexus-home>/sonatype-work/nexus3/etc/nexus.properties or <nexus-home>/etc/nexus.properties. Search for the property 'nexus.orient.binaryListenerEnabled' and verify its value.
    Affected if The property exists and is set to 'true' (the vulnerability only applies when this non-default setting is enabled)

A user is affected only if they run Nexus Repository Manager 3 version 3.0.0-3.70.5 AND have manually enabled the non-default nexus.orient.binaryListenerEnabled=true setting in their configuration.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the nexus.orient.binaryListenerEnabled setting if enabled, and upgrade to a patched version once available from Sonatype.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5189 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-5189 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