# CVE-2026-120954: Silent element-count truncation via 32-bit bit-length overflow in packed-bit vector views


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-120954, UBUNTU-CVE-2026-120954

## What is CVE-2026-120954?

CVE-2026-120954 is a medium-severity vulnerability in MongoDB C Driver, published on 3 Nov 2026. 

### Official description

A weakness in the BSON library's handling of a specialized binary vector data type allows an arithmetic wraparound when computing the number of elements described by an oversized attacker-supplied value. On builds where the platform word size is 32 bits, an application that parses untrusted BSON data can be made to process only a small fraction of the supplied elements while the operation reports success, producing results that disagree with byte-oriented accessors and with 64-bit builds of the same library. No authentication or user interaction is required beyond getting the application to parse the data. The impact is limited to data integrity; memory safety is not affected and no information is disclosed.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-120954?


## How do I fix CVE-2026-120954?

Upgrade to a fixed version.

## Is CVE-2026-120954 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120954 and fix it if it is affected.

What it is: CVE-2026-120954 is a medium-severity vulnerability in MongoDB C Driver, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120954 in the wild and no public exploit code.

Affected product: MongoDB 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-2026-120954/ (Markdown: https://insights.sbomify.com/CVE-2026-120954/index.md)
```

## Sources

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

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