VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

CouchbaseNetClient: vulnerability history, versions and safety

CouchbaseNetClient is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Jun 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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 CouchbaseNetClient vulnerabilities

Vulert verdict on CouchbaseNetClient 3.10.0 i

Updated on 23 Oct 2026

Careful: 3.10.0 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 Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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 3.10.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 18 Jun 2025 i
  • Highest CVSS 4.9 i
  • With no published fix 1 i
  • Stars 284 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by NuGet, 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 CouchbaseNetClient, 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
3.10.0 08 Oct 2026 M1 Apache-2.0 No Details →
3.9.6 04 Sep 2026 M1 Apache-2.0 No Details →
3.9.5 10 Aug 2026 M1 Apache-2.0 No Details →
3.9.4 16 Jul 2026 M1 Apache-2.0 No Details →
3.9.3 04 Jun 2026 M1 Apache-2.0 No Details →
3.9.3-buildbot-r10410 04 Jun 2026 M1 Apache-2.0 No Details →
3.9.2 06 May 2026 M1 Apache-2.0 No Details →
3.9.1 08 Apr 2026 M1 Apache-2.0 No Details →
3.9.0 26 Feb 2026 M1 Apache-2.0 No Details →
3.9.0-rc3 11 Dec 2025 M1 Apache-2.0 No Details →
3.8.1 11 Nov 2025 M1 Apache-2.0 No Details →
3.8.0 20 Aug 2025 M1 Apache-2.0 No Details →
3.7.2 29 May 2025 M1 Apache-2.0 No Details →
3.7.1 07 May 2025 M1 Apache-2.0 No Details →
3.7.0 07 Apr 2025 M1 Apache-2.0 No Details →
3.6.6 10 Mar 2025 M1 Apache-2.0 No Details →
3.6.5 18 Jan 2025 M1 Apache-2.0 No Details →
3.6.4 08 Nov 2024 M1 Apache-2.0 No Details →
3.5.5 11 Oct 2024 M1 Apache-2.0 No Details →
3.6.3 19 Sep 2024 M1 Apache-2.0 No Details →
3.6.2 22 Jul 2024 M1 Apache-2.0 No Details →
3.5.3 22 Jul 2024 M1 Apache-2.0 No Details →
3.6.1 03 Jul 2024 M1 Apache-2.0 No Details →
3.6.0 14 Jun 2024 M1 Apache-2.0 No Details →
3.5.2 03 May 2024 M1 Apache-2.0 No Details →
3.5.1 16 Apr 2024 M1 Apache-2.0 No Details →
3.5.1-rc5 12 Apr 2024 M1 Apache-2.0 No Details →
3.4.15 09 Feb 2024 M1 Apache-2.0 No Details →
3.4.14 17 Jan 2024 M1 Apache-2.0 No Details →
3.4.14-rc3 08 Dec 2023 M1 Apache-2.0 No Details →
3.4.13 09 Nov 2023 M1 Apache-2.0 No Details →
3.4.12 04 Oct 2023 M1 Apache-2.0 No Details →
3.4.11 12 Sep 2023 M1 Apache-2.0 No Details →
3.4.9 21 Jul 2023 M1 Apache-2.0 No Details →
3.4.8 13 Jun 2023 M1 Apache-2.0 No Details →
3.4.6 12 May 2023 M1 Apache-2.0 No Details →
3.4.5 20 Apr 2023 M1 Apache-2.0 No Details →
3.4.4 10 Mar 2023 M1 Apache-2.0 No Details →
3.4.3 09 Feb 2023 M1 Apache-2.0 No Details →
3.4.2 13 Jan 2023 M1 Apache-2.0 No Details →
3.4.1 09 Dec 2022 M1 Apache-2.0 No Details →
3.4.0 09 Nov 2022 M1 Apache-2.0 No Details →
3.3.6 06 Oct 2022 M1 Apache-2.0 No Details →
3.3.5 17 Sep 2022 M1 Apache-2.0 No Details →
3.3.4 02 Aug 2022 M1 Apache-2.0 No Details →
3.3.3 11 Jul 2022 M1 Apache-2.0 No Details →
3.3.2 16 Jun 2022 M1 Apache-2.0 No Details →
3.3.1 04 May 2022 M1 Apache-2.0 No Details →
3.2.9 07 Apr 2022 M1 Apache-2.0 No Details →
3.2.8 02 Mar 2022 M1 Apache-2.0 No Details →
3.2.7 01 Feb 2022 M1 Apache-2.0 No Details →
2.7.27 01 Feb 2022 M1 Apache-2.0 No Details →
3.2.6 12 Jan 2022 M1 Apache-2.0 No Details →
3.2.5 10 Dec 2021 M1 Apache-2.0 No Details →
3.2.4 02 Nov 2021 M1 Apache-2.0 No Details →
3.2.3 07 Oct 2021 M1 Apache-2.0 No Details →
3.2.2 15 Sep 2021 M1 Apache-2.0 No Details →
3.2.0 28 Jul 2021 M1 Apache-2.0 No Details →
2.7.26 01 Jun 2021 M1 Apache-2.0 No Details →
3.1.7 01 Jun 2021 M1 Apache-2.0 No Details →
3.1.6 24 May 2021 M1 Apache-2.0 No Details →
2.7.25 13 May 2021 M1 Apache-2.0 No Details →
2.7.24 10 Apr 2021 M1 Apache-2.0 No Details →
3.1.4 09 Apr 2021 M1 Apache-2.0 No Details →
3.1.3 04 Mar 2021 M1 Apache-2.0 No Details →
3.1.2 11 Feb 2021 M1 Apache-2.0 No Details →
3.1.1 14 Jan 2021 M1 Apache-2.0 No Details →
2.7.23 13 Jan 2021 M1 Apache-2.0 No Details →
3.1.0 01 Dec 2020 M1 Apache-2.0 No Details →
2.7.22 10 Nov 2020 M1 Apache-2.0 No Details →
3.0.7 03 Nov 2020 M1 Apache-2.0 No Details →
3.0.6 13 Oct 2020 M1 Apache-2.0 No Details →
3.0.5 02 Sep 2020 M1 Apache-2.0 No Details →
2.7.21 02 Sep 2020 M1 Apache-2.0 No Details →
2.7.20 10 Aug 2020 M1 Apache-2.0 No Details →
3.0.4 06 Aug 2020 M1 Apache-2.0 No Details →
3.0.3 14 Jul 2020 M1 Apache-2.0 No Details →
3.0.2 18 Jun 2020 M1 Apache-2.0 No Details →
2.7.18 10 Jun 2020 M1 Apache-2.0 No Details →
3.0.1 13 May 2020 M1 Apache-2.0 No Details →
2.7.17 05 May 2020 M1 Apache-2.0 No Details →
3.0.0 01 Apr 2020 M1 Apache-2.0 No Details →
2.7.16 11 Feb 2020 M1 Apache-2.0 No Details →
3.0.0-beta4 21 Jan 2020 M1 Apache-2.0 No Details →
3.0.0-beta3 20 Dec 2019 M1 Apache-2.0 No Details →
2.7.15 05 Dec 2019 M1 Apache-2.0 No Details →
3.0.0-beta2 21 Nov 2019 M1 Apache-2.0 No Details →
2.7.13 05 Nov 2019 M1 Apache-2.0 No Details →
3.0.0-beta1 04 Oct 2019 M1 Apache-2.0 No Details →
2.7.12 12 Sep 2019 M1 Apache-2.0 No Details →
2.7.11 07 Aug 2019 M1 Apache-2.0 No Details →
3.0.0-alpha5 30 Jul 2019 M1 Apache-2.0 No Details →
2.7.10 15 Jul 2019 M1 Apache-2.0 No Details →
3.0.0-alpha4 11 Jun 2019 M1 Apache-2.0 No Details →
2.7.8 04 Jun 2019 M1 Apache-2.0 No Details →
2.7.7 08 May 2019 M1 Apache-2.0 No Details →
3.0.0-alpha3 26 Apr 2019 M1 Apache-2.0 No Details →
2.7.6 05 Apr 2019 M1 Apache-2.0 No Details →
3.0.0-alpha2 20 Mar 2019 M1 Apache-2.0 No Details →
2.7.5 12 Mar 2019 M1 Apache-2.0 No Details →
2.7.4 06 Feb 2019 M1 — No Details →
2.7.3 12 Jan 2019 M1 — No Details →
2.7.2 05 Dec 2018 M1 — No Details →
2.7.1 07 Nov 2018 M1 — No Details →
2.7.0 02 Oct 2018 M1 — No Details →
2.6.2 10 Sep 2018 M1 — No Details →
2.6.1 13 Aug 2018 M1 — No Details →
2.6.0 10 Jul 2018 M1 — No Details →
2.5.12 12 Jun 2018 M1 — No Details →
2.5.10 02 May 2018 M1 — No Details →
2.6.0-beta 13 Apr 2018 M1 — No Details →
2.5.9 03 Apr 2018 M1 — No Details →
2.5.8 17 Mar 2018 M1 — No Details →
2.5.5 06 Feb 2018 M1 — No Details →
2.5.4 10 Jan 2018 M1 — No Details →
2.5.3 08 Dec 2017 M1 — No Details →
2.5.2 20 Oct 2017 M1 — No Details →
2.4.8 03 Aug 2017 M1 — No Details →
2.4.7 11 Jul 2017 M1 — No Details →
2.4.5 16 May 2017 M1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for CouchbaseNetClient

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-49015: Couchbase .NET SDK Hostname Verification Bypass Vulnerability 4.9 medium No fix published 18 Jun 2025

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 CouchbaseNetClient

Is CouchbaseNetClient safe to use?

Vulert records 1 vulnerabilities for CouchbaseNetClient in NuGet: 0 critical, 0 high, 1 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is CouchbaseNetClient's Vulert package health score?

Vulert scores CouchbaseNetClient 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 CouchbaseNetClient affected?

Yes. 3.10.0, 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 CouchbaseNetClient should I use?

3.10.0 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 CouchbaseNetClient have?

1 vulnerability is recorded for CouchbaseNetClient in the NuGet ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new CouchbaseNetClient vulnerabilities disclosed?

0 vulnerabilities were recorded for CouchbaseNetClient in the last 12 months, and the oldest entry in this database dates to 18 Jun 2025. 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 CouchbaseNetClient 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 CouchbaseNetClient for upcoming vulnerabilities?

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