Read the docs

Deserialization allow-list bypass in MongoDB C# Driver BSON handling

Priority LOW 11CWE-502Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Code execution
Confidentiality · integrity · availability
None · Low · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-502.

Summary

MongoDB C# Driver from 2.21.0 before 3.14.0 can be bypassed in its deserialization type-restriction control for BSON content. The check that recognizes compiler-generated anonymous types relies on an overly permissive heuristic, so types outside the intended allow-list can be constructed. An unauthorized party who can place crafted BSON content into a deserialization path that uses loosely typed members can populate those types with attacker-supplied values, which can cause unexpected object state and errors in application logic. The weakness is classified as CWE-502.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

A deserialization type-restriction control in the BSON serialization component can be bypassed because the check used to recognize a class of compiler-generated types relies on an overly permissive heuristic rather than a precise identification. An unauthorized party able to supply BSON content that an application later deserializes into a loosely typed member can cause types outside the intended allow-list to be constructed and populated with unauthorized party-supplied values inside the consuming application. This can lead to unexpected object state and errors in downstream application logic. No elevated privileges beyond the ability to place unauthorized party-influenced content in the deserialization path are required.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00181 7th percentileScored 2026-11-17
Fix Fixed C# Driver (MongoDB): 3.14.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
MongoDBC# Driver2.21.0 to before 3.14.03.14.0Patch availableCNA
  • C# Driver VendorMongoDB Affected 2.21.0 to before 3.14.0 Fixed in 3.14.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:mongodb:c\#_driver:*:*:*:*:*:*:*:*——MongoDB
  • cpe:2.3:a:mongodb:c\#_driver:*:*:*:*:*:*:*:* Versions — — ·MongoDB

Remediation

Upgrade MongoDB C# Driver to version 3.14.0 or later, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA C# Driver (MongoDB) Fixed in 3.14.0

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-126839
  2. 2026-11-13 Alias added: GHSA-48g7-vc36-5wgx
  3. 2026-11-17 CISA SSVC decision points changed

References

  • TI-2019-08023 Remote code execution in mongo-express via toBSON endpoints KEVCVSS 3.1CRITICAL 9.9
  • TI-2025-13542 Zlib header length mismatch in MongoDB Server allows memory read KEVCVSS 4.0HIGH 8.7
  • TI-2026-89295 MongoDB Server Missing Authorization Check in Replication Administrative Command CVSS 4.0HIGH 8.6
  • TI-2026-89289 Incorrect authorization in MongoDB Server allows admin access CVSS 4.0HIGH 8.6
  • TI-2026-79432 BSON output corruption via out-of-range binary subtype in MongoDB C# Driver CVSS 4.0MEDIUM 6.9
  • TI-2026-79424 NoSQL command injection via mismatched BSON length in MongoDB C# Driver CVSS 4.0MEDIUM 6.9
See all 411 →

Sources