BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-0755High confidence

MongoDB C Driver bson library may be susceptible to buffer overflow

MongoDB Inc · libbson

8.4HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.77% for the current model date.

Compensating controls

  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs MongoDB Inc libbson and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

6 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcemongo-c-driverVendor fix publishedDebian records a fixed source-package version for this release.1.27.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelibbson-xs-perlVendor fix publishedDebian records a fixed source-package version for this release.0.8.4-2+deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcemongo-c-driverVendor fix publishedDebian records a fixed source-package version for this release.1.23.1-1+deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcemongo-c-driverVendor fix publishedDebian records a fixed source-package version for this release.1.27.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcemongo-c-driverVendor fix publishedDebian records a fixed source-package version for this release.1.27.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsmongo-c-driverVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1.26.0-1.1ubuntu2+esm1Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-6467

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
01

What, why and how

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

What

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

Why

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

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

Why

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Heap-based Buffer Overflow → disrupt the affected service
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-122 ↗

CWE-122: Heap-based Buffer Overflow. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedDenial of serviceCWE-122
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0587MongoDB: Schwachstelle ermöglicht Codeausführung und DoS

Ein lokaler Angreifer kann eine Schwachstelle in MongoDB ausnutzen, um einen Denial of Service zu verursachen und potentiell beliebigen Code auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250320Security Bulletin 20 Mar 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 20 Mar 2025, published on 20 March 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0083Multiples vulnérabilités dans les produits IBM

cord?id=CVE-2022-3510 Référence CVE CVE-2024-23454 https://www.cve.org/CVERecord?id=CVE-2024-23454 Référence CVE CVE-2024-47535 https://www.cve.org/CVERecord?id=CVE-2024-47535 Référence CVE CVE-2024-49350 https://www.cve.org/CVERecord?id=CVE-2024-49350 Référence CVE CVE-2024-49828 https://www.cve.org/CVERecord?id=CVE-2024-49828 Référence CVE CVE-2024-51473 https://www.cve.org/CVERecord?id=CVE-2024-51473 Référence CVE CVE-2024-52894 https://www.cve.org/CVERecord?id=CVE-2024-52894 Référence CVE CVE-2024-52903 https://www.cve.org/CVERecord?id=CVE-2024-52903 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2025-0755 https://www.cve.org/CVERecord?id=CVE-2025-0755 Référence CVE CVE-2025-0915 https://www.cve.org/CVERecord?id=CVE-2025-0915 Référence CVE CVE-2025-1000 https://www.cve.org/CVERecord?id=CVE-2025-1000 Référence CVE CVE-2025-1493 https://www.cve.org/CVERecord?id=CVE-2025-1493 Référence CVE CVE-2025-1992 https://www.cve.org/CVERecord?id=CVE-2025-1992 Référence CVE CVE-2025-24970 https://www.cve.org/CVERecord?id=CVE-2025-24970 Référence CVE CVE-2025-2518 https://www.cve.org/CVERecord?id=CVE-2025-2518 Référence CVE CVE-2025-25193 https://www.cve.org/CVERecord?id=CVE-2025-25193 Référence CVE CVE-2025-2533 https://www.cve.org/CVERecord?id=CVE-2025-253

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0760Multiples vulnérabilités dans les produits IBM

cve.org/CVERecord?id=CVE-2024-57699 Référence CVE CVE-2024-6484 https://www.cve.org/CVERecord?id=CVE-2024-6484 Référence CVE CVE-2024-6485 https://www.cve.org/CVERecord?id=CVE-2024-6485 Référence CVE CVE-2024-6762 https://www.cve.org/CVERecord?id=CVE-2024-6762 Référence CVE CVE-2024-6763 https://www.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2024-6827 https://www.cve.org/CVERecord?id=CVE-2024-6827 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2024-8184 https://www.cve.org/CVERecord?id=CVE-2024-8184 Référence CVE CVE-2024-9823 https://www.cve.org/CVERecord?id=CVE-2024-9823 Référence CVE CVE-2025-0755 https://www.cve.org/CVERecord?id=CVE-2025-0755 Référence CVE CVE-2025-1647 https://www.cve.org/CVERecord?id=CVE-2025-1647 Référence CVE CVE-2025-21756 https://www.cve.org/CVERecord?id=CVE-2025-21756 Référence CVE CVE-2025-21759 https://www.cve.org/CVERecord?id=CVE-2025-21759 Référence CVE CVE-2025-21887 https://www.cve.org/CVERecord?id=CVE-2025-21887 Référence CVE CVE-2025-21966 https://www.cve.org/CVERecord?id=CVE-2025-21966 Référence CVE CVE-2025-22004 https://www.cve.org/CVERecord?id=CVE-2025-22004 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0651Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-21147 Référence CVE CVE-2024-27267 https://www.cve.org/CVERecord?id=CVE-2024-27267 Référence CVE CVE-2024-45490 https://www.cve.org/CVERecord?id=CVE-2024-45490 Référence CVE CVE-2024-45491 https://www.cve.org/CVERecord?id=CVE-2024-45491 Référence CVE CVE-2024-45492 https://www.cve.org/CVERecord?id=CVE-2024-45492 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-49342 https://www.cve.org/CVERecord?id=CVE-2024-49342 Référence CVE CVE-2024-49343 https://www.cve.org/CVERecord?id=CVE-2024-49343 Référence CVE CVE-2024-50602 https://www.cve.org/CVERecord?id=CVE-2024-50602 Référence CVE CVE-2025-0755 https://www.cve.org/CVERecord?id=CVE-2025-0755 Référence CVE CVE-2025-24970 https://www.cve.org/CVERecord?id=CVE-2025-24970 Référence CVE CVE-2025-27607 https://www.cve.org/CVERecord?id=CVE-2025-27607 Référence CVE CVE-2025-30472 https://www.cve.org/CVERecord?id=CVE-2025-30472 Référence CVE CVE-2025-33092 https://www.cve.org/CVERecord?id=CVE-2025-33092 Référence CVE CVE-2025-36097 https://www.cve.org/CVERecord?id=CVE-2025-36097 Référence CVE CVE-2025-47278 https://www.cve.org/CVERecord?id=CVE-2025-47278 Référence CVE CVE-2025-48387 https://www.cve.org/CVERecord?id=CVE-2025-48387 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0222Vulnérabilité dans MongoDB C Driver

Une vulnérabilité a été découverte dans MongoDB C Driver. Elle permet à un attaquant de provoquer un déni de service.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-014279MongoDB Inc. の libbson および MongoDB におけるヒープベースのバッファオーバーフローの脆弱性

MongoDB Inc. の libbson および MongoDB には、ヒープベースのバッファオーバーフローの脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
  • libbson: < 1.27.5
  • MongoDB Server: 8.0 < 8.0.1, 7.0 < 7.0.16
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 18 Mar 2025 · Last source change 3 Nov 2025, 19:35 UTC · CWE-122 · Heap-based Buffer Overflow

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-6467
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-0755 · cve.blacktree.nl