Is mongoose 8.22 vulnerable?

npm · 2 releases from 8.22.0 to 8.22.1 · latest mongoose is 9.11.4 · checked 1 Nov 2026

Yes: 1 known advisory

Yes. mongoose 8.22.1, the last 8.22 release, is affected by 1 known security advisory (1 medium), including CVE-2026-73562. 1 more affects earlier 8.22.x releases. Upgrade to 8.24.1 or later to fix all of them.

Upgrade with:npm install mongoose@8.24.1

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting mongoose 8.22.1

  • MediumCVE-2026-73562GHSA-664h-wqgq-64gw24 Jul 2026

    Mongoose: Prototype pollution in mongoose update casting via __proto__-prefixed dotted path (Schema._getSchema/path getter)

    Affected
    <6.13.10 · >=7.0.0 <7.8.10 · >=8.0.0 <8.24.1 · >=9.0.0 <9.7.2
    Fixed in
    6.13.10, 7.8.10, 8.24.1, 9.7.2

Fixed within 8.22.x, affecting earlier releases

  • HighCVE-2026-42334GHSA-wpg9-53fq-2r8h5 May 2026

    Mongoose's Improper Sanitization of $nor in sanitizeFilter May Allow NoSQL Injection

    Affected
    <6.13.9 · >=7.0.0 <7.8.9 · >=8.0.0 <8.22.1 · >=9.0.0 <9.1.6
    Fixed in
    6.13.9, 7.8.9, 8.22.1, 9.1.6

Which of your client projects are still on mongoose 8.22?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact mongoose version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other mongoose versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.