NoSQL injection of JavaScript-executing query operators via unsafe-by-default operator guard

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps MongoDB Inc./Mongoid (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for MongoDB Inc./Mongoid.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 18, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 18, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 18, 2026

Sources and claim methodology

• Source referencejira.mongodb.org

Related CVEs

• Server-side JavaScript injection via string query criteria bypassing the strict operator allowlistSame mongodb inc./mongoid package
• Denial of service via unbounded regex matching in Mongoid's in-memory query matcherSame mongodb inc./mongoid package
• Data deletion and attribute disclosure via field-name method injection in in-memory queriesSame mongodb inc./mongoid package
• Silent plaintext persistence via unresolved callable database name in encryption schema mapSame mongodb inc./mongoid package
• Plaintext storage of encrypted fields via skipped embedded models in encryption schema generationSame mongodb inc./mongoid package
• Document deletion and process crash via unvalidated method-name dispatch in atomic pop operationSame mongodb inc./mongoid package