{"answers":{"affected":"4 open source packages ship an affected version, including @apostrophecms/db-connect and apostrophe.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113666 exists.","fix":"Upgrade @apostrophecms/db-connect to 1.1.0 or later.","what":"CVE-2026-113666 is a high-severity vulnerability in @apostrophecms apostrophe, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-113666 and fix it if it is affected.\n\nWhat it is: CVE-2026-113666 is a high-severity vulnerability in @apostrophecms apostrophe, published on 20 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113666 exists.\n\nAffected packages and fixed versions:\n- @apostrophecms/db-connect (npm): affected all versions; fixed in 1.1.0\n- @apostrophecms/db-connect (npm): affected all versions; fixed in 1.1.0\n- apostrophe (npm): affected all versions; fixed in 4.33.0\n- apostrophe (npm): affected all versions; fixed in 4.33.0\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-113666/ (Markdown: https://insights.sbomify.com/CVE-2026-113666/index.md)","id":"CVE-2026-113666","markdown":"https://insights.sbomify.com/CVE-2026-113666/index.md","name":"CVE-2026-113666","record":{"aliases":["GHSA-j5rq-xfvr-p969"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"},{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"ApostropheCMS is an open-source Node.js content management system. Prior to 1.1.0 of db-connect and 4.33.0 of ApostropheCMS, an account with view-draft access can submit a projection exclusion path that traverses through a constructor prototype chain to a shared prototype member when a consumer uses a SQLite, PostgreSQL, or multipostgres adapter and has a matching document. Every editing role has view-draft access, while guestApiAccess broadens this prerequisite to any logged-in account. The unsetNestedField helper then deletes the shared runtime member, causing persistent process-wide integrity and availability effects; the default MongoDB adapter is not affected. This issue is fixed in db-connect 1.1.0 and ApostropheCMS 4.33.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"ApostropheCMS: Authenticated projection-exclusion prototype-member deletion in @apostrophecms/db-connect causes process-wide denial of service","id":"CVE-2026-113666","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"ApostropheCMS: CAPTCHA response token not URL-encoded","id":"CVE-2026-113667"},"packages":[{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"@apostrophecms/db-connect","purl":null,"source":"GHSA-j5rq-xfvr-p969"},{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"@apostrophecms/db-connect","purl":"pkg:npm/%40apostrophecms/db-connect","source":"GHSA-j5rq-xfvr-p969"},{"ecosystem":"npm","fixed":["4.33.0"],"introduced":["0"],"last_affected":[],"package":"apostrophe","purl":null,"source":"GHSA-j5rq-xfvr-p969"},{"ecosystem":"npm","fixed":["4.33.0"],"introduced":["0"],"last_affected":[],"package":"apostrophe","purl":"pkg:npm/apostrophe","source":"GHSA-j5rq-xfvr-p969"}],"prev":{"headline":"ApostropheCMS: Missing Authorization on Notification PATCH/DELETE Endpoints","id":"CVE-2026-113665"},"products":["apostrophe","db-connect"],"published":"2026-10-20","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["@apostrophecms","apostrophecms"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-113666/"}