{"answers":{"affected":"4 open source packages ship an affected version, including mongoose.","exploited":"There is no known exploitation of CVE-2026-125116 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-125116 is a medium-severity vulnerability in Automattic mongoose, published on 9 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-125116 and fix it if it is affected.\n\nWhat it is: CVE-2026-125116 is a medium-severity vulnerability in Automattic mongoose, published on 9 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-125116 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mongoose (npm): affected all versions; 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-125116/ (Markdown: https://insights.sbomify.com/CVE-2026-125116/index.md)","id":"CVE-2026-125116","markdown":"https://insights.sbomify.com/CVE-2026-125116/index.md","name":"CVE-2026-125116","record":{"aliases":["GHSA-wr5m-5jph-8m96"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"description":"Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.12, 7.8.13, 8.24.7, and 9.11.4, Mongoose uses attacker-controlled discriminator key values, including the default __t field, to index plain-object registries such as Model.discriminators and schema.discriminators without requiring an own property. Values such as constructor, toString, or hasOwnProperty can therefore resolve to inherited built-in functions instead of a registered discriminator, causing type confusion in model construction, document creation, hydration, query and update casting, embedded discriminators, and populate operations. In the bulkWrite() insertOne path with skipValidation enabled, a constructor value can cause a raw input object to be stored without schema casting or strict filtering, and a stored poisoned document can make every query that hydrates it fail until the document is removed. The weakness reads inherited properties but does not modify Object.prototype and is not prototype pollution. 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: Discriminator key values matching inherited properties (e.g. __t: 'constructor') bypass schema casting and can poison collections","id":"CVE-2026-125116","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":4,"n_references":11,"next":{"headline":"Mongoose walks into inherited properties when hydrating, setting, and merging, allowing overwrites of built-in functions (denial of service) and shared schema state","id":"CVE-2026-125117"},"nickname":null,"packages":[{"ecosystem":"npm","fixed":["6.13.12"],"introduced":["0"],"last_affected":[],"package":"mongoose","purl":null,"source":"GHSA-wr5m-5jph-8m96"},{"ecosystem":"npm","fixed":["7.8.13"],"introduced":["7.0.0"],"last_affected":[],"package":"mongoose","purl":null,"source":"GHSA-wr5m-5jph-8m96"},{"ecosystem":"npm","fixed":["8.24.7"],"introduced":["8.0.0"],"last_affected":[],"package":"mongoose","purl":null,"source":"GHSA-wr5m-5jph-8m96"},{"ecosystem":"npm","fixed":["9.11.4"],"introduced":["9.0.0"],"last_affected":[],"package":"mongoose","purl":null,"source":"GHSA-wr5m-5jph-8m96"}],"prev":{"headline":"@novu/application-generic: `validateUrlSsrf` permits CGNAT (100.64.0.0/10) destinations — affects Workflow HTTP request step + Webhook filter condition","id":"CVE-2026-125115"},"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-09","vendors":["Automattic"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-125116/"}