VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

couchbase: vulnerability history, versions and safety

couchbase is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 120 releases, from Jun 2022 to Jul 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 U3
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all couchbase vulnerabilities

Vulert verdict on couchbase 4.6.3 i

Updated on 23 Oct 2026

Careful: 4.6.3 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.6.3 — affected i
  • Vulnerabilities on record 4 over 3 years · 0 in the last year i
  • Latest disclosure 29 Jul 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Depended on by 38 packages i
  • Stars 247 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for couchbase, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.6.3 25 Aug 2026 U1 Apache-2.0 No Details →
4.6.3rc1 25 Aug 2026 U1 Apache-2.0 No Details →
4.5.1 21 Aug 2026 U1 Apache-2.0 No Details →
4.5.1rc1 21 Aug 2026 U1 Apache-2.0 No Details →
4.6.2 18 Jun 2026 U1 Apache-2.0 No Details →
4.6.2rc1 17 Jun 2026 U1 Apache-2.0 No Details →
4.6.1 29 Apr 2026 U1 Apache-2.0 No Details →
4.6.1rc1 29 Apr 2026 U1 Apache-2.0 No Details →
4.6.0 31 Mar 2026 U1 Apache-2.0 No Details →
4.6.0rc2 31 Mar 2026 U1 Apache-2.0 No Details →
4.5.0 30 Sep 2025 U1 Apache-2.0 No Details →
4.5.0rc1 29 Sep 2025 U1 Apache-2.0 No Details →
4.4.1 29 Sep 2025 U1 Apache-2.0 No Details →
4.4.1rc1 26 Sep 2025 U1 Apache-2.0 No Details →
4.4.0 02 Jun 2025 U1 Apache-2.0 No Details →
4.4.0rc1 02 Jun 2025 U1 Apache-2.0 No Details →
4.3.6 15 May 2025 U1 Apache-2.0 No Details →
4.3.6rc1 15 May 2025 U1 Apache-2.0 No Details →
4.3.5 28 Jan 2025 U1 Apache-2.0 No Details →
4.3.5rc1 28 Jan 2025 U1 Apache-2.0 No Details →
4.3.4 25 Nov 2024 U1 Apache-2.0 No Details →
4.3.4rc1 25 Nov 2024 U1 Apache-2.0 No Details →
4.3.3 22 Oct 2024 U1 Apache-2.0 No Details →
4.3.3rc1 22 Oct 2024 U1 Apache-2.0 No Details →
4.3.2 24 Sep 2024 U1 Apache-2.0 No Details →
4.3.2rc1 24 Sep 2024 U1 Apache-2.0 No Details →
4.3.1 27 Aug 2024 U1 Apache-2.0 No Details →
4.3.1rc1 26 Aug 2024 U1 Apache-2.0 No Details →
4.3.0 27 Jun 2024 U1 Apache-2.0 No Details →
4.3.0rc1 27 Jun 2024 U1 Apache-2.0 No Details →
4.2.1 18 Apr 2024 U1 Apache-2.0 No Details →
4.2.1rc1 18 Apr 2024 U1 Apache-2.0 No Details →
4.2.0 14 Mar 2024 U1 Apache-2.0 No Details →
4.2.0rc1 14 Mar 2024 U1 Apache-2.0 No Details →
4.1.12 02 Mar 2024 U1 Apache-2.0 No Details →
4.1.12rc1 23 Feb 2024 U1 Apache-2.0 No Details →
4.1.11 02 Feb 2024 U1 Apache-2.0 No Details →
4.1.11rc1 02 Feb 2024 U1 Apache-2.0 No Details →
4.1.10 03 Jan 2024 U1 Apache-2.0 No Details →
4.1.10rc1 03 Jan 2024 U1 Apache-2.0 No Details →
4.1.9 15 Nov 2023 U1 Apache-2.0 No Details →
4.1.9rc1 10 Nov 2023 U1 Apache-2.0 No Details →
4.1.8 25 Aug 2023 U1 Apache-2.0 No Details →
4.1.8rc1 25 Aug 2023 U1 Apache-2.0 No Details →
4.1.7 08 Aug 2023 U1 Apache-2.0 No Details →
4.1.7rc1 08 Aug 2023 U1 Apache-2.0 No Details →
4.1.6 13 Jul 2023 U1 Apache-2.0 No Details →
4.1.6rc2 13 Jul 2023 U1 Apache-2.0 No Details →
4.1.5 09 Jun 2023 U1 Apache-2.0 No Details →
4.1.4 09 May 2023 U1 Apache-2.0 No Details →
4.1.3 09 Mar 2023 U1 Apache-2.0 No Details →
4.1.2 10 Feb 2023 U1 Apache-2.0 No Details →
4.1.2rc2 10 Feb 2023 U1 Apache-2.0 No Details →
4.1.1 14 Dec 2022 U1 Apache-2.0 No Details →
4.1.0 04 Nov 2022 U1 Apache-2.0 No Details →
4.0.5 07 Oct 2022 U1 Apache-2.0 No Details →
4.0.4 09 Sep 2022 U1 Apache-2.0 No Details →
4.0.3 03 Aug 2022 U1 Apache-2.0 No Details →
4.0.2 29 Jun 2022 U1 Apache-2.0 No Details →
4.0.1 09 Jun 2022 U1 Apache-2.0 No Details →
4.0.0 06 May 2022 U1 Apache-2.0 No Details →
4.0.0rc1 06 May 2022 U1 Apache-2.0 No Details →
3.2.7 23 Mar 2022 U1 Apache-2.0 No Details →
3.2.6 03 Feb 2022 U1 Apache-2.0 No Details →
3.2.5 12 Jan 2022 U2 Apache-2.0 No Details →
3.2.5rc1 12 Jan 2022 U2 Apache-2.0 No Details →
3.2.5.dev1 12 Jan 2022 U2 Apache-2.0 No Details →
3.2.4 07 Dec 2021 U2 Apache-2.0 No Details →
3.2.3 03 Nov 2021 U2 Apache-2.0 No Details →
3.2.2 12 Oct 2021 U2 Apache-2.0 No Details →
3.2.1 10 Sep 2021 U2 Apache-2.0 No Details →
3.2.0 27 Jul 2021 U2 Apache-2.0 No Details →
3.1.3 14 Jun 2021 U2 Apache-2.0 No Details →
3.1.2 12 May 2021 U2 Apache-2.0 No Details →
3.1.1 26 Apr 2021 U2 Apache-2.0 No Details →
3.1.0 22 Apr 2021 U2 Apache-2.0 No Details →
3.0.10 04 Mar 2021 U2 Apache-2.0 No Details →
3.0.9 02 Feb 2021 U2 Apache-2.0 No Details →
3.0.8 13 Jan 2021 U2 Apache-2.0 No Details →
3.0.7 08 Dec 2020 U2 Apache-2.0 No Details →
3.0.6 03 Nov 2020 U2 Apache-2.0 No Details →
3.0.5 04 Sep 2020 U2 Apache-2.0 No Details →
3.0.4 11 Aug 2020 U2 Apache-2.0 No Details →
3.0.4b1 22 Jul 2020 U2 Apache-2.0 No Details →
3.0.3 16 Jul 2020 U2 Apache-2.0 No Details →
3.0.3b20 15 Jul 2020 U2 Apache-2.0 No Details →
3.0.2 14 Jul 2020 U2 Apache-2.0 No Details →
3.0.2b9 14 Jul 2020 C1 U3 Apache-2.0 No Details →
3.0.2b7 14 Jul 2020 C1 U3 Apache-2.0 No Details →
3.0.2b6 14 Jul 2020 C1 U3 Apache-2.0 No Details →
3.0.2b5 14 Jul 2020 C1 U3 Apache-2.0 No Details →
3.0.2b4 14 Jul 2020 C1 U3 Apache-2.0 No Details →
3.0.2b2 14 Jul 2020 C1 U3 Apache-2.0 No Details →
3.0.2b1 14 Jul 2020 C1 U3 Apache-2.0 No Details →
3.0.1 12 Jun 2020 C1 U3 Apache-2.0 No Details →
2.5.12 05 May 2020 U2 Apache-2.0 No Details →
3.0.0 01 May 2020 C1 U3 Apache-2.0 No Details →
2.5.11 02 Mar 2020 U2 Apache-2.0 No Details →
3.0.0b3 21 Jan 2020 U2 Apache-2.0 No Details →
3.0.0b2 30 Dec 2019 U2 Apache-2.0 No Details →
2.5.10 17 Dec 2019 U2 — No Details →
2.5.9 06 Nov 2019 U2 — No Details →
3.0.0b1 11 Oct 2019 U2 — No Details →
3.0.0a6 28 Sep 2019 U2 — No Details →
2.5.8 03 Sep 2019 U2 — No Details →
3.0.0a5 27 Aug 2019 U2 — No Details →
2.5.7 06 Aug 2019 U2 — No Details →
3.0.0a4 12 Jul 2019 U2 — No Details →
3.0.0a3 05 Jul 2019 U2 — No Details →
2.5.6 02 Jul 2019 U2 — No Details →
3.0.0a2 18 Jun 2019 U2 — No Details →
2.5.5 05 Jun 2019 U2 — No Details →
2.5.4 05 Feb 2019 U2 — No Details →
2.5.3 09 Jan 2019 U2 — No Details →
2.5.2 04 Dec 2018 U2 — No Details →
2.5.1 06 Nov 2018 U2 — No Details →
2.5.0 02 Oct 2018 U2 — No Details →
2.4.2 07 Sep 2018 U2 — No Details →
2.4.1 17 Aug 2018 U2 — No Details →
2.4.0 04 Jul 2018 U2 — No Details →

The newest 120 of 509 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2023 1
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for couchbase

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-32563: Couchbase Sync Gateway X.509 Client Cert Authentication Bypass 9.8 critical 3.0.2 11 Jun 2022
CVE-2023-45875: Private Key Leak in Couchbase Server 7.2.0 7.5 high No fix published 08 Nov 2023
CVE-2025-52490: Couchbase Sync Gateway Cleartext Password Exposure Vulnerability 7.3 high 3.2.6 29 Jul 2025
CVE-2022-32563: Privilege Escalation in Couchbase Sync Gateway N/A unrated 3.0.2 10 Jun 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About couchbase

Is couchbase safe to use?

Vulert records 4 vulnerabilities for couchbase in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 3 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is couchbase's Vulert package health score?

Vulert scores couchbase 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of couchbase affected?

Yes. 4.6.3, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of couchbase should I use?

4.6.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does couchbase have?

4 vulnerabilities are recorded for couchbase in the PyPI ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new couchbase vulnerabilities disclosed?

0 vulnerabilities were recorded for couchbase in the last 12 months, and the oldest entry in this database dates to 10 Jun 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of couchbase are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor couchbase for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the couchbase version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.