Skip to content

← Public intelligence

PyPI package

couchbase

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.3PyPIAmendedPublished

    Couchbase Sync Gateway shows cleartext passwords in redacted and unredacted output

    CVE-2025-52490 · GHSA-pqhp-4xfc-hjgq

    Affected
    • PyPI couchbase < 3.2.6
    Fixed in
    3.2.6· Vendor fix available
    Issue
    An issue was discovered in Couchbase Sync Gateway before 3.2.6. In sgcollectinfooptions.log and syncgateway.log, there are cleartext passwords in redacted and unredacted output.

    Recommended action: Upgrade to 3.2.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. Critical, CVSS 9.3PyPIAmendedPublished

    Couchbase Sync Gateway admin credentials not verified when using X.509 client cert authentication

    CVE-2022-32563 · GHSA-9266-j9v3-q4j5

    Affected
    • PyPI couchbase >= 3.0.0, < 3.0.2
    Fixed in
    3.0.2· Vendor fix available
    Issue
    An issue was discovered in Couchbase Sync Gateway 3.x before 3.0.2. Admin credentials are not verified when using X.509 client-certificate authentication from Sync Gateway to Couchbase Server. When Sync Gateway is configured to authenticate with Couchbase Server using X.509 client certificates, the admin credentials provided to the Admin REST API are ignored, resulting in privilege escalation for unauthenticated users. The Public REST API is not impacted by this issue. A workaround is to replace X.509 certificate based authentication with Username and Password authentication inside the bootstrap configuration.

    Recommended action: Upgrade to 3.0.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →