NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Mongoose Prototype Pollution vulnerabilityGHSA-9m93-w8w6-76hh

CRITICALFix: Automattic/mongoose@e29578d

GHSA-9m93-w8w6-76hh is a critical-severity (CVSS 10) CWE-1321 vulnerability in mongoose. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for mongoose — see the affected versions and patch details below.

Also known asBIT-mongoose-2023-3696CVE-2023-3696
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9m93-w8w6-76hh.

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk
0.00%0.57%1.14%1.71%0.5%1.2%May 26Sep 26Nov 26

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

3 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

Prototype Pollution in GitHub repository automattic/mongoose prior to 7.3.3, 6.11.3, and 5.13.20.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
📦npmmongoose≥ 7.0.0&&< 7.3.37.3.3npm install mongoose@7.3.3
📦npmmongoose≥ 6.0.0&&< 6.11.36.11.3npm install mongoose@6.11.3
📦npmmongooseall versions5.13.20npm install mongoose@5.13.20

Affected Products

1 product · 3 configurations
Application
mongoosemongoosejs
≥ 7.0.0 && < 7.3.4
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update mongoose to 7.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9m93-w8w6-76hh is resolved across your whole dependency graph.

  3. 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

Prototype Pollution in GitHub repository automattic/mongoose prior to 7.3.3, 6.11.3, and 5.13.20.
O3 Security · Impact-Aware SCA

Is GHSA-9m93-w8w6-76hh in your dependencies?

Find it across npm, including transitive dependencies.

Mongoose Prototype Pollution vulnerability (Critical 10)