GHSA-664H-WQGQ-64GW

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

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Check user-controlled updates for own __proto__ properties before passing to Mongoose

References

Are there any links users can visit to find out more?

What kind of vulnerability is it? Who is impacted?

Prototype pollution in update casting: passing a user-controlled update to a Mongoose update, like MyModel.updateOne(filter, req.body), can cause Mongoose to set $fullPath and $parentSchemaDocArray on Object.prototype.

Example:

const mongoose = require('mongoose');
console.log('before:', Object.prototype.$fullPath);            // undefined

const User = mongoose.model('User', new mongoose.Schema({ name: String }));
const malicious = JSON.parse('{"$set": {"__proto__.x": "anything"}}');   // attacker-controlled update

const q = User.updateOne({}, {});
try { q._castUpdate(malicious); } catch (e) { /* throws AFTER the pollution side-effect */ }

console.log('after :', Object.prototype.$fullPath);            // "__proto__"
console.log('enumerable:', Object.prototype.propertyIsEnumerable('$fullPath'));  // true
console.log('fresh {}:', ({}).$fullPath);                      // "__proto__"

GHSA-664H-WQGQ-64GW has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.13.10, 7.8.10, 8.24.1, 9.7.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Has the problem been patched? What versions should users upgrade to?

9.7.2, 8.24.1. 7.8.10, 6.13.10

1. What is GHSA-664H-WQGQ-64GW? GHSA-664H-WQGQ-64GW is a medium-severity security vulnerability in mongoose (npm), affecting versions < 6.13.10. It is fixed in 6.13.10, 7.8.10, 8.24.1, 9.7.2.
2. How severe is GHSA-664H-WQGQ-64GW? GHSA-664H-WQGQ-64GW has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of mongoose are affected by GHSA-664H-WQGQ-64GW? mongoose (npm) versions < 6.13.10 is affected.
4. Is there a fix for GHSA-664H-WQGQ-64GW? Yes. GHSA-664H-WQGQ-64GW is fixed in 6.13.10, 7.8.10, 8.24.1, 9.7.2. Upgrade to this version or later.
5. Is GHSA-664H-WQGQ-64GW exploitable, and should I be worried? Whether GHSA-664H-WQGQ-64GW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-664H-WQGQ-64GW is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-664H-WQGQ-64GW?
   • Upgrade mongoose to 6.13.10 or later
   • Upgrade mongoose to 7.8.10 or later
   • Upgrade mongoose to 8.24.1 or later
   • Upgrade mongoose to 9.7.2 or later

Other vulnerabilities in mongoose