Skip to main content
VulnerabilityPublished

CVE-2025-49015: couchbase.netclient · CVE-2025-49015 is a

Affects couchbase.netclientSource CVE Database V5

0

Not known to be exploited · CVSS 4.9 Medium : upgrade to 3.7.1 when convenient.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.7.1
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade couchbase.netclient to 3.7.1.

Affected software

ProductAffectedFixed in
NuGetcouchbase.netclientpkg:nuget/couchbase.netclientOther threatsAffected
  • <3.7.1
Fixed in
  • 3.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Couchbase .NET SDK version 3.7.1 and later. Users should upgrade to version 3.7.1 or newer to ensure proper hostname verification is enabled by default. No other mitigations are specified.

Description

CVE-2025-49015 is a vulnerability in the Couchbase .NET SDK client library versions before 3.7.1. The issue involves improper hostname verification for TLS certificates, where the SDK incorrectly uses IP addresses instead of hostnames due to a misconfigured default setting. This flaw could allow an attacker to bypass hostname verification during TLS connections.

References

Community reviews

Loading reviews…