Skip to content
Fencer Intel
high 7.0

CVE-2022-2564 in the critical feed json

Prototype Pollution in automattic/mongoose

published 4y ago modified 2mo ago also BIT-mongoose-2022-2564 , EUVD-2022-6328 , GHSA-f825-f98c-gj3g

cvss
7.0
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
31.3%
EPSS 31.3% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

Prototype Pollution in GitHub repository automattic/mongoose prior to 6.4.6.

Patch / fix

  • npm mongoose 5.13.15, 6.4.6
  • bitnami mongoose 5.13.15, 6.4.6
  • automattic automattic/mongoose 6.4.6

Is CVE-2022-2564 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

31.30% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/055be524-9296-4b2f-b68d-6d5b810d1ddd referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/Automattic/mongoose/blob/51e758541763b6f14569744ced15cc23ab8b50c6/lib/schema.js#L88-L141 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 7.0 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
GitHub 3.1 7.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm mongoose
>=6.0.0, <6.4.6
<5.13.15
6.4.6
5.13.15
bitnami mongoose
<5.13.15
>=6.0.0, <6.4.6
5.13.15
6.4.6

Affected products

  • automattic automattic/mongoose

Classification

Weakness
  • CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.