How severe is GHSA-pcrw-h46h-c93h?

GHSA-pcrw-h46h-c93h has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-pcrw-h46h-c93h?

GHSA-pcrw-h46h-c93h affects the following packages: mongoose (npm), mongoose (npm), mongoose (npm), mongoose (npm). Ecosystems affected: npm.

How do I fix GHSA-pcrw-h46h-c93h?

Update mongoose to 6.13.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pcrw-h46h-c93h is resolved across your whole dependency graph.

How do I detect GHSA-pcrw-h46h-c93h in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mongoose, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pcrw-h46h-c93h if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-pcrw-h46h-c93h actively exploited in the wild?

No public exploit code has been indexed for GHSA-pcrw-h46h-c93h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-pcrw-h46h-c93h?

GHSA-pcrw-h46h-c93h has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pcrw-h46h-c93h?

GHSA-pcrw-h46h-c93h is classified as CWE-943 (CWE-943). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pcrw-h46h-c93h published, and has it been updated?

GHSA-pcrw-h46h-c93h was published on November 10, 2026 and was last updated on November 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

Mongoose: sanitizeFilter not applied on countDocumentsGHSA-pcrw-h46h-c93h

CRITICALFix: Automattic/mongoose@7e912af

GHSA-pcrw-h46h-c93h is a critical-severity (CVSS 9.8) CWE-943 vulnerability in mongoose. A fix is available for mongoose — see the affected versions and patch details below.

Also known asCVE-2026-125120

Published

Nov 10, 2026

Updated

Nov 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

21Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

mongoosenpm

8.9Mdownloads / week

Description

Impact

sanitizeFilter is Mongoose's mechanism for protecting against query selector injection attacks. In older versions of Mongoose, sanitizeFilter was not applied for countDocuments() queries.

Patches

Patches have been released for all supported Mongoose major release lines. Please upgrade to the following versions depending on which major version of Mongoose applications are using.

^9.9.2
^8.24.3
^7.8.12
^6.13.11

Workarounds

Middleware:

mongoose.plugin(function() {
  schema.pre('countDocuments', function() {
    // This will always apply `sanitizeFilter` on `countDocuments`
    mongoose.sanitizeFilter(this.getFilter());
  });
});

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mongoose`	all versions	6.13.11`npm install mongoose@6.13.11`
📦npm	`mongoose`	≥ 7.0.0&&< 7.8.12	7.8.12`npm install mongoose@7.8.12`
📦npm	`mongoose`	≥ 8.0.0&&< 8.24.3	8.24.3`npm install mongoose@8.24.3`
📦npm	`mongoose`	≥ 9.0.0&&< 9.9.2	9.9.2`npm install mongoose@9.9.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mongoose, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mongoose to 6.13.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pcrw-h46h-c93h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact `sanitizeFilter` is Mongoose's mechanism for protecting against query selector injection attacks. In older versions of Mongoose, `sanitizeFilter` was not applied for `countDocuments()` queries. ### Patches Patches have been released for all supported Mongoose major release lines. Please upgrade to the following versions depending on which major version of Mongoose applications are using. 1. `^9.9.2` 2. `^8.24.3` 3. `^7.8.12` 4. `^6.13.11` ### Workarounds Middleware: ```javascript mongoose.plugin(function() { schema.pre('countDocuments', function() { // This will always