dbcve.org
Couchbase ServerApplication · Couchbase

CVE-2025-46619

HIGH · 7.6 CVSS v3.1 Published 2025-04-30
Fix available
A fix is available. Upgrade to 7.2.7 / 7.6.4 or later.
See remediation →
82/100
Remediation priority · High
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 security issue has been discovered in Couchbase Server before 7.6.4 and fixed in v.7.6.4 and v.7.2.7 for Windows that could allow unauthorized access to sensitive files. Depending on the level of privileges, this vulnerability may grant access to files such as /etc/passwd or /etc/shadow.

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

This is a file path traversal vulnerability in Couchbase Server that allows unauthorized access to sensitive files on the underlying system. Depending on the privilege level of the Couchbase service account, an attacker could read system files such as /etc/passwd or /etc/shadow, potentially exposing user credentials and system configuration details.

MitigationUpgrade Couchbase Server to version 7.6.4 or 7.2.7 (or later) to remediate this vulnerability. Prioritize patching on systems where Couchbase runs with elevated privileges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Couchbase ServerApplication
Affected:>= 2.0.0, < 7.2.7>= 7.6.0, < 7.6.4

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

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 Couchbase Server is installed
    Look for Couchbase installation directories (/opt/couchbase on Linux, C:\Program Files\Couchbase on Windows) or run 'ps aux | grep couchbase' to find running Couchbase processes
    Affected if Couchbase Server process is running or Couchbase directories exist on the system
  2. Determine the installed Couchbase Server version
    Check the version file in the Couchbase installation directory (e.g., cat /opt/couchbase/VERSION.txt or C:\Program Files\Couchbase\Server\VERSION.txt), or run '/opt/couchbase/bin/couchbase-server --version'
    Affected if The installed version matches the affected ranges: >=2.0.0 and <7.2.7, OR >=7.6.0 and <7.6.4
  3. Check if Couchbase web console or REST API is accessible
    Attempt to access the Couchbase admin interface (port 8091 by default) or query the REST API endpoint (e.g., curl http://localhost:8091/pools)
    Affected if The Couchbase service is exposed via network and accepts requests from the attacker (even localhost if untrusted local users exist)
  4. Verify Couchbase service account privileges
    Check the user the Couchbase service runs as (e.g., 'ps aux | grep couchbase' on Linux or check Service Properties on Windows) and verify if it has elevated file system permissions
    Affected if Couchbase runs as root, administrator, or an account with permission to read sensitive system files like /etc/passwd or /etc/shadow

Your environment is affected if Couchbase Server is running a version between 2.0.0-7.2.6 or 7.6.0-7.6.3, especially if the service has elevated privileges that allow reading system files.

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
Upgrade available Upgrade to 7.2.7 / 7.6.4 or later
Fixed in 7.2.77.6.4
Interim mitigation

Upgrade Couchbase Server to version 7.6.4 or 7.2.7 (or later) to remediate this vulnerability. Prioritize patching on systems where Couchbase runs with elevated privileges.

Recommended fix High confidence

Couchbase Server 7.2.7 (for 7.2.x line) or 7.6.4 (for 7.6.x line) or later in respective branches

  1. Identify your current Couchbase Server version using the Couchbase Admin Console or CLI (couchbase-cli server-info)
  2. Determine which upgrade path applies: if running 7.2.0-7.2.6, upgrade to 7.2.7 or later; if running 7.6.0-7.6.3, upgrade to 7.6.4 or later
  3. Review Couchbase upgrade documentation for your current version to ensure compatibility
  4. Perform a full backup of all cluster data before upgrading
  5. Follow the standard Couchbase Server upgrade procedure for your deployment type (rolling upgrade or offline upgrade)
  6. After upgrade, verify the server version confirms 7.2.7+ or 7.6.4+ is running
  7. Test that normal cluster operations function correctly post-upgrade
Caveat Rolling upgrades supported within same major version; major version upgrades may require additional migration steps; review breaking changes in Couchbase 7.2 and 7.6 release notes

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

Fix this in Couchbase Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46619 — 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-2025-46619 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