dbcve.org
LibbsonApplication · MongoDB

CVE-2025-0755

HIGH · 7.5 CVSS v3.1 Published 2025-03-18
Fix available
A fix is available. Upgrade to 1.27.5 / 7.0.16 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The various bson_append functions in the MongoDB C driver library may be susceptible to buffer overflow when performing operations that could result in a final BSON document which exceeds the maximum allowable size (INT32_MAX), resulting in a segmentation fault and possible application crash. This issue affected libbson versions prior to 1.27.5, MongoDB Server v8.0 versions prior to 8.0.1 and MongoDB Server v7.0 versions prior to 7.0.16

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 · high confidence

The bson_append functions in libbson (MongoDB C driver) lack proper bounds checking when appending data to BSON documents, allowing creation of documents exceeding INT32_MAX (2GB). This triggers buffer overflow, causing segmentation faults and application crashes.

MitigationUpgrade to libbson 1.27.5+, MongoDB Server 7.0.16+, or 8.0.1+ to patch the vulnerable bson_append functions.

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
LibbsonApplication
Affected:< 1.27.5
MongoDBDatabase / datastore
Affected:>= 7.0.0, < 7.0.16= 8.0.0

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

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

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. Check installed libbson version
    Run 'pkg-config --modversion libbson' or check your application's dependency list for the libbson version
    Affected if The version is less than 1.27.5
  2. Check MongoDB Server version
    Run 'mongod --version' to see the server version
    Affected if The version is 7.0.0 through 7.0.15, or exactly 8.0.0
  3. Identify if libbson is embedded in application
    Search your application binaries or source code for libbson symbols using 'ldd <binary>' or grep for 'bson_append' in linked libraries
    Affected if libbson is statically linked and version cannot be determined or is below 1.27.5
  4. Check for large BSON document creation code
    Review application code for calls to bson_append, bson_append_utf8, bson_append_document, or similar bson_append functions that handle user-controlled data
    Affected if Code uses bson_append functions to build documents from external input without size limits

You are affected if your environment uses libbson below 1.27.5 or MongoDB Server 7.0.0-7.0.15 or 8.0.0, and your application creates BSON documents using the vulnerable bson_append functions with data that could exceed 2GB.

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 1.27.5 / 7.0.16 or later
Fixed in 1.27.57.0.16
Interim mitigation

Upgrade to libbson 1.27.5+, MongoDB Server 7.0.16+, or 8.0.1+ to patch the vulnerable bson_append functions.

Recommended fix High confidence

libbson: 1.27.5+ | MongoDB Server v8.0: 8.0.1+ | MongoDB Server v7.0: 7.0.16+

  1. 1. Identify the current version of libbson or MongoDB Server in use by running 'mongod --version' or checking the libbson library version
  2. 2. For libbson users: Upgrade to libbson version 1.27.5 or later by updating the dependency in your project
  3. 3. For MongoDB Server v8.0 users: Upgrade to MongoDB Server version 8.0.1 or later
  4. 4. For MongoDB Server v7.0 users: Upgrade to MongoDB Server version 7.0.16 or later
  5. 5. After upgrading, verify the new version is installed by running 'mongod --version'
  6. 6. Test application functionality to ensure the upgrade does not introduce regressions

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

Fix this in Libbson Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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