# CVE-2026-120825: An authorization weakness in the aggregation framework of MongoDB Server may allow an authenticated user holding only basic database privile


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-jhg3-8vrj-4c5q

## What is CVE-2026-120825?

CVE-2026-120825 is a high-severity vulnerability in MongoDB Server, published on 10 Nov 2026. 

### Official description

An authorization weakness in the aggregation framework of MongoDB Server may allow an authenticated user holding only basic database privileges to read the contents of collections in a database for which they have not been granted read access. The privilege evaluation performed while a view definition is validated does not cover a nested portion of the supplied pipeline, so the resulting view returns data the user is otherwise refused. This may result in unintended access to data, including stored authentication material.

Weakness: CWE-862 (Missing Authorization)

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


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

No fix has been published for CVE-2026-120825 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120825 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120825 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120825 is a high-severity vulnerability in MongoDB Server, published on 10 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120825 exists.

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

## Sources

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

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