# CVE-2026-120815: Incorrect Authorization Check in MongoDB Server Localhost Exception Leads to Unauthorized Administrative Access


- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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-vfjp-mf5p-687x

## What is CVE-2026-120815?

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

### Official description

An incorrect authorization check in the MongoDB Server authorization subsystem may allow an unauthenticated party with local host access to obtain administrative privileges on a database server that has authorization enabled. This may result in unintended access to stored data and credentials, unintended modification of data, and loss of availability of the server.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-120815 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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