← Back to results
Vulnerability record · public intelligence
CVE-2026-81528
MEDIUM

NoSQL injection via array replacement bypassing update shape validation in driver write path

Published Aug 27, 2026 · Updated Oct 23, 2026

Severity · CVSSMEDIUM · 5.4
Known exploitationNot listed
EPSS / likelihood0.28%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

NoSQL injection via array replacement bypassing update shape validation in driver write path

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. jira.mongodb.org ↗
  2. www.nuget.org ↗

Record history

Published Aug 27, 2026 · Last refreshed Oct 23, 2026