{"answers":{"affected":"2 open source packages ship an affected version, including @keystone-6/core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33326 in the wild and no public exploit code.","fix":"Upgrade @keystone-6/core to 6.5.2 or later.","what":"CVE-2026-33326 is a medium-severity missing authorization vulnerability in keystonejs keystone, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33326 and fix it if it is affected.\n\nWhat it is: CVE-2026-33326 is a medium-severity missing authorization vulnerability in keystonejs keystone, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33326 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @keystone-6/core (npm): affected all versions; fixed in 6.5.2\n- @keystone-6/core (npm): affected all versions; fixed in 6.5.2\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-33326/ (Markdown: https://insights.sbomify.com/CVE-2026-33326/index.md)","id":"CVE-2026-33326","markdown":"https://insights.sbomify.com/CVE-2026-33326/index.md","name":"CVE-2026-33326","record":{"aliases":["GHSA-cgcg-q9jh-5pr2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js CMS","requires_auth":"low_privilege","summary":"Attackers can bypass field-level access controls in Keystone CMS findMany queries to confirm the existence of records via protected field values.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"keystone","vendor":"keystonejs"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Keystone is a content management system for Node.js. Prior to version 6.5.2, {field}.isFilterable access control can be bypassed in findMany queries by passing a cursor. This can be used to confirm the existence of records by protected field values. The fix for CVE-2025-46720 (field-level isFilterable bypass for update and delete mutations) added checks to the where parameter in update and delete mutations however the cursor parameter in findMany was not patched and accepts the same UniqueWhere input type. This issue has been patched in version 6.5.2.","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":"@keystone-6/core: `isFilterable` bypass via `cursor` parameter in findMany","id":"CVE-2026-33326","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Possible integer overflow leading to potential heap-based buffer overflow","id":"CVE-2026-33327"},"packages":[{"ecosystem":"npm","fixed":["6.5.2"],"introduced":["0"],"last_affected":[],"package":"@keystone-6/core","purl":null,"source":"GHSA-cgcg-q9jh-5pr2"},{"ecosystem":"npm","fixed":["6.5.2"],"introduced":["0"],"last_affected":[],"package":"@keystone-6/core","purl":"pkg:npm/%40keystone-6/core","source":"GHSA-cgcg-q9jh-5pr2"}],"prev":{"headline":"SQLBot prompt injection allows arbitrary SQL execution and remote code execution","id":"CVE-2026-33324"},"products":["keystone"],"published":"2026-03-24","related":[{"cvss_score":9.8,"headline":"NODE_ENV in Keystone defaults to development with esbuild","id":"CVE-2022-39382","kev_date_added":null,"published":"2022-11-03"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-29354","kev_date_added":null,"published":"2022-05-16"},{"cvss_score":9.1,"headline":"@keystone-6/core vulnerable to field-level access-control bypass for multiselect field","id":"CVE-2022-39322","kev_date_added":null,"published":"2022-10-25"},{"cvss_score":8.8,"headline":"Cross-Site Request Forgery (CSRF) in keystone","id":"CVE-2017-16570","kev_date_added":null,"published":"2017-11-06"},{"cvss_score":8.8,"headline":"Keystone is vulnerable to CSV injection","id":"CVE-2017-15879","kev_date_added":null,"published":"2017-10-24"},{"cvss_score":7.5,"headline":"Authentication Weakness in keystone","id":"CVE-2015-9240","kev_date_added":null,"published":"2018-05-29"},{"cvss_score":7.1,"headline":"Cross-site Scripting (XSS) - Reflected in keystonejs/keystone","id":"CVE-2022-0087","kev_date_added":null,"published":"2022-01-11"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-25","vendors":["keystonejs"]},"summary":"Attackers can bypass field-level access controls in Keystone CMS findMany queries to confirm the existence of records via protected field values.","url":"https://insights.sbomify.com/CVE-2026-33326/"}