# CVE-2025-14911: Integer Overflow in GridFS chunkSize Leading to Heap Allocation Failure

> An integer overflow in the MongoDB C driver allows attackers to cause heap allocation failures via malformed GridFS metadata, leading to denial of service.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jan 2026
- **Updated:** 26 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-14911, GHSA-pc4j-j33v-hr73

## What is CVE-2025-14911?

CVE-2025-14911 is a high-severity vulnerability in MongoDB Mongo-c-driver, published on 27 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

User-controlled chunkSize metadata from MongoDB lacks appropriate validation allowing malformed GridFS metadata to overflow the bounding container.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2025-14911?


## How do I fix CVE-2025-14911?

Upgrade to a fixed version.

## Is CVE-2025-14911 being exploited?

There is no known exploitation of CVE-2025-14911 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14911 and fix it if it is affected.

What it is: CVE-2025-14911 is a high-severity vulnerability in MongoDB Mongo-c-driver, published on 27 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14911 in the wild and no public exploit code.

Affected product: MongoDB Mongo-c-driver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14911/ (Markdown: https://insights.sbomify.com/CVE-2025-14911/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14911
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14911
- OSV: https://osv.dev/vulnerability/CVE-2025-14911

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14911/
Summaries are generated and may contain mistakes; the official description above is the record.