Medium severity · published Aug 27, 2026
CVE-2026-81528
NoSQL injection via array replacement bypassing update shape validation in driver write path
5.4
CVSS
0.3%
EPSS
No
On KEV
Description
A MongoDB C# driver document-replacement code path omits the element-name/shape validation that the equivalent write paths apply, so a value supplied as a replacement is forwarded to the server without neutralization of query-language special elements. An application that passes untrusted, loosely-typed input as a replacement value therefore allows that input to be interpreted by the database as update logic rather than as data, executing under the application's own database credentials. Applications using strongly-typed document mappings are not affected.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
Low
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 20% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
MO
MongoDB · MongoDB
2.9.0 before 3.11.1 · source: vendor
CD
C# Driver · Mongodb
2.10.0 before 3.11.1 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-81528
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-81528
Vendor Advisory
https://jira.mongodb.org/browse/CSHARP-6158
Product
https://www.nuget.org/packages/MongoDB.Driver/3.11.1
More from MongoDB
9.9
CVE-2019-10758
MongoDB mongo-express Remote Code Execution Vulnerability
7.5
CVE-2025-14847
Zlib compressed protocol header length confusion may allow memory read
9.8
CVE-2026-19001
MongoDB BI Connector ODBC driver may write outside an allocated buffer when handling oversized catalog object names
9.8
CVE-2025-3085
A MongoDB server under specific conditions running on Linux with TLS and CRL revocation status checking enabled, fails to check the revocation status of the intermediate…
9.8
CVE-2024-8654
MongoDB Server may access non-initialized region of memory leading to unexpected behaviour
