Live › vulnerability › CVE-2026-114652
Go to dashboardThe MongoDB C# Driver's update-statement builder can treat application-supplied values as query or update logic instead of literal data. A user who can influence those values can modify or remove stored data the application did not intend to change.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications that use the MongoDB C# Driver and pass values influenced by application users into the update-statement builder can have stored data changed or removed. The sources do not say which builder methods are affected, so apps with no user-influenced update input are likely lower risk. Teams that only read data or use fixed update statements can likely skip it.
No product ranges from the sources yet.
dotnet list package | grep MongoDB.Driverdotnet list package and compare it against the fixed version, which the sources do not nameEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A data-query-logic neutralization weakness in the update-statement construction component of the MongoDB C# Driver can cause application-supplied values to be interpreted as query/update logic rather than as literal data. An application user who can influence the content of values that the application passes into the affected builder surface, without any special privilege beyond ordinary read-write application access, may cause stored data to be modified or removed in ways the application never intended. The result is unauthorized integrity impact on the affected application data; there is no direct loss of confidentiality or availability of the database service.
This page as .md · .json · in your agent: get_signal("CVE-2026-114652")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.