Applications
CVE-2026-125120
Mongoose countDocuments selector-injection can bypass authorization and break app logic.
Major vulnerability. Mongoose is a widely used Node.js MongoDB ODM; a 9.8 RCE-adjacent selector-injection can undermine authorization and app logic across many web apps, warranting broad attention.
- CVSS
- 9.8Criticalscored by the publisher (CNA)
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- No score yet
- Fix
- Patch availablesee the advisories in the references
- Published
- 9 Nov 2026analysed here 12 Nov 2026
Summary
Impact
Query selector injection in countDocuments() allows attacker-controlled operators to alter counts and bypass authorization or application logic based on those counts.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Automattic mongoose | < 6.13.11>= 7.0.0 and < 7.8.12>= 8.0.0 and < 8.24.3>= 9.0.0 and < 9.9.2Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- Mongoose < 6.13.11
- Mongoose < 7.8.12
- Mongoose < 8.24.3
- Mongoose < 9.9.2
- Node.js applications using Mongoose countDocuments() with sanitizeFilter enabled
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
Timeline
- 9 Nov 2026Published
- 9 Nov 2026CVE record last updatedsame day later
- 12 Nov 2026Analysed by vulneraibility.com3 days later
Common questions
Is CVE-2026-125120 being exploited?
Not confirmed. CVE-2026-125120 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-125120?
CVE-2026-125120 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-125120?
Yes. A fix has been recorded for CVE-2026-125120. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-125120 affect?
CVE-2026-125120 affects Mongoose < 6.13.11, Mongoose < 7.8.12, Mongoose < 8.24.3, Mongoose < 9.9.2, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-125120?
Upgrade to Mongoose >=6.13.11/7.8.12/8.24.3/9.9.2 and validate/sanitize user filters.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
9 references in the CVE record, grouped by the tags the record gives them.
Other links (9)
- github.com /Automattic/mongoose/security/advisories/GHSA-pcrw-h46h-c93h
- github.com /Automattic/mongoose/commit/7e912af3fac52cb0eea4cd71e24d65318916831a
- github.com /Automattic/mongoose/commit/8b10d5760bb181f5bf5d01495cde161c8aed0557
- github.com /Automattic/mongoose/commit/b1df045aab076b740fdaec14a15a44c694b85b7d
- github.com /Automattic/mongoose/commit/b5003d3915db1cf9209c38a4b93cf3a92cddd710
- github.com /Automattic/mongoose/releases/tag/6.13.11
Show 3 more
- github.com /Automattic/mongoose/releases/tag/7.8.12
- github.com /Automattic/mongoose/releases/tag/8.24.3
- github.com /Automattic/mongoose/releases/tag/9.9.2
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.