# CVE-2026-92756: MongoDB Entity Framework Core Provider encryption settings bypass

Source: https://junglewise.ai/threats/cve-2026-92756-mongodb-entity-framework-core-provider-encryption-settings-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-17. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-92756 · Severity: medium · CVSS 5.5 · Published 2026-09-17

Applications using MongoDB's Entity Framework Core Provider may inadvertently disable encryption protections when combining independent and provider-specific encryption settings, causing sensitive data fields to be stored unencrypted in the database. This silent failure of encryption could expose protected information without warning to application owners.

Technologies: [MongoDB Entity Framework Core Provider](https://junglewise.ai/threats/technologies/entity-framework-core-provider). Vendors: [MongoDB](https://junglewise.ai/threats/vendors/mongodb).

## Quick answers

**Is CVE-2026-92756 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-92756 being exploited in the wild.

**How severe is CVE-2026-92756?** Medium severity, with a CVSS score of 5.5, published 17 September 2026.

**Which products and versions are affected?** MongoDB Entity Framework Core Provider.

**Is there a fix for CVE-2026-92756?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-92756 attacked?** It is attacked with local access.

**Am I affected by CVE-2026-92756?** Check whether you run MongoDB Entity Framework Core Provider. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The MongoDB Entity Framework Core Provider contains a configuration flaw where conflicting encryption settings—when independent encryption settings are combined with the provider's own encryption settings—cause TLS and schema-map settings to be silently dropped. This results in encrypted fields being stored in plaintext in the database. The vulnerability is a logic error in the encryption configuration handling, requiring the specific combination of both types of encryption settings to trigger. No user interaction or authentication is required to be vulnerable; affected applications will automatically lose encryption protections during normal operation.

## Affected products

- MongoDB Entity Framework Core Provider

## Timeline

- 2026-09-17: disclosed

## References

- [https://jira.mongodb.org/browse/EF-388](https://jira.mongodb.org/browse/EF-388)

## Related threats

- [MongoDB Entity Framework Core provider expression injection in bulk update](https://junglewise.ai/threats/cve-2026-120567-the-mongodb-entity-framework-core-provider-does-not-neutralize)
- [MongoDB Entity Framework Core credential exposure in logging](https://junglewise.ai/threats/cve-2026-92758-mongodb-entity-framework-core-credential-exposure-in-logging)
- [MongoDB Entity Framework Core Provider field encryption bypass via database name misconfiguration](https://junglewise.ai/threats/cve-2026-92757-mongodb-entity-framework-core-provider-field-encryption-bypass)