# CVE-2026-120567: EF Core provider: pipeline-form ExecuteUpdate evaluates a user string setter as a $-field reference


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 6 Nov 2026

## What is CVE-2026-120567?

CVE-2026-120567 is a low-severity vulnerability in MongoDB Entity Framework Core Provider, published on 3 Nov 2026. 

### Official description

The MongoDB Entity Framework Core provider does not neutralize special elements in values passed to SetProperty when an ExecuteUpdate call also contains a setter that reads the entity being updated. In that case the update is sent as an aggregation pipeline, and a caller-supplied string beginning with $ is evaluated as an expression rather than stored as data. A party who can influence such a value may modify or remove fields in the records being updated, or copy other fields of the same record into them.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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


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

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

## Is CVE-2026-120567 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120567 is a low-severity vulnerability in MongoDB Entity Framework Core Provider, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120567 in the wild and no public exploit code.

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

## Sources

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

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