{"answers":{"affected":"4 open source packages ship an affected version, including mongoose.","exploited":"There is no known exploitation of CVE-2026-125119 in the wild and no public exploit code.","exposure":"","fix":"Upgrade mongoose to a fixed version for your release line: 6.13.12, 7.8.13, 8.24.7 or 9.11.4.","what":"CVE-2026-125119 is a high-severity vulnerability in Automattic mongoose, published on 9 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-125119 and fix it if it is affected.\n\nWhat it is: CVE-2026-125119 is a high-severity vulnerability in Automattic mongoose, published on 9 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-125119 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mongoose (npm): affected from 6.0.0; fixed in 6.13.12\n- mongoose (npm): affected from 7.0.0; fixed in 7.8.13\n- mongoose (npm): affected from 8.0.0; fixed in 8.24.7\n- mongoose (npm): affected from 9.0.0; fixed in 9.11.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-125119/ (Markdown: https://insights.sbomify.com/CVE-2026-125119/index.md)","id":"CVE-2026-125119","markdown":"https://insights.sbomify.com/CVE-2026-125119/index.md","name":"CVE-2026-125119","record":{"aliases":["GHSA-gg4r-jv3p-qx3c"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-943","name":"Improper Neutralization of Special Elements in Data Query Logic"}],"description":"Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. From 6.0.0 until 6.13.12, 7.8.13, 8.24.7, and 9.11.4, Mongoose stores the connection-level sanitizeFilter option in Connection.config, but Query.prototype._castConditions() and query casting check other option locations and do not read that configuration. An application that enables sanitizeFilter through mongoose.connect() or createConnection() and passes an attacker-controlled object into a query filter therefore receives a connection that reports the defense as enabled while query selector objects remain unsanitized. A crafted password value using a query operator can match an account record without the expected literal password, while global configuration through mongoose.set('sanitizeFilter') and per-query Model.find().sanitizeFilter() remain unaffected. This issue is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Mongoose: Connection-level sanitizeFilter not applied","id":"CVE-2026-125119","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":4,"n_references":9,"next":{"headline":"Mongoose: sanitizeFilter not applied on countDocuments","id":"CVE-2026-125120"},"nickname":null,"packages":[{"ecosystem":"npm","fixed":["6.13.12"],"introduced":["6.0.0"],"last_affected":[],"package":"mongoose","purl":null,"source":"GHSA-gg4r-jv3p-qx3c"},{"ecosystem":"npm","fixed":["7.8.13"],"introduced":["7.0.0"],"last_affected":[],"package":"mongoose","purl":null,"source":"GHSA-gg4r-jv3p-qx3c"},{"ecosystem":"npm","fixed":["8.24.7"],"introduced":["8.0.0"],"last_affected":[],"package":"mongoose","purl":null,"source":"GHSA-gg4r-jv3p-qx3c"},{"ecosystem":"npm","fixed":["9.11.4"],"introduced":["9.0.0"],"last_affected":[],"package":"mongoose","purl":null,"source":"GHSA-gg4r-jv3p-qx3c"}],"prev":{"headline":"Mongoose: Prototype pollution via Schema.prototype.virtual()","id":"CVE-2026-125118"},"products":["mongoose"],"published":"2026-11-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-12","vendors":["Automattic"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-125119/"}