# CVE-2026-120806: Authorization role-graph corruption via no-op cleanup filters in dropAllRolesFromDatabase


- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/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-6j54-23c6-25cx

## What is CVE-2026-120806?

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

### Official description

A flaw in MongoDB Server's user management commands may lead to incomplete cleanup of role authorization data when roles are dropped from a database. Due to incorrect internal query predicates, the drop operation removes role definitions but fails to remove stale references in user and role documents. If a role with the same name is subsequently recreated with different privileges, previously associated users may silently inherit the new role's privileges without an explicit grant or corresponding audit event. Exploitation requires authenticated access with database administrative privileges on the target database.

Weakness: CWE-459 (Incomplete Cleanup)

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


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

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

## Is CVE-2026-120806 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120806 is a high-severity vulnerability in MongoDB Server, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120806 in the wild and no public exploit code.

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

## Sources

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

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