{"answers":{"affected":"2 open source packages ship an affected version, including @keystone-6/core.","exploited":"There is no known exploitation of CVE-2026-63421 in the wild and no public exploit code.","fix":"Upgrade @keystone-6/core to 6.5.3 or later.","what":"CVE-2026-63421 is a high-severity vulnerability in keystonejs keystone, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63421 and fix it if it is affected.\n\nWhat it is: CVE-2026-63421 is a high-severity vulnerability in keystonejs keystone, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-63421 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.3\n- @keystone-6/core (npm): affected all versions; fixed in 6.5.3\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-63421/ (Markdown: https://insights.sbomify.com/CVE-2026-63421/index.md)","id":"CVE-2026-63421","markdown":"https://insights.sbomify.com/CVE-2026-63421/index.md","name":"CVE-2026-63421","record":{"aliases":["GHSA-cqmq-8755-7xvh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js CMS","requires_auth":"none","summary":"Attackers can bypass GraphQL take limits using negative values to retrieve excessive records, potentially causing resource exhaustion.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","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:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-480","name":"Use of Incorrect Operator"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Keystone is a content management system for Node.js. Prior to 6.5.3, the findMany resolver in packages/core/src/lib/core/queries/resolvers.ts compares the signed take argument directly with graphql.maxTake, allowing a remote unauthenticated GraphQL client to provide a negative take value whose magnitude exceeds the configured bound. The bypass also applies to relationship queries and can return more records than the developer intended, potentially exhausting service resources. This issue is fixed in version 6.5.3.","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: `graphql.maxTake` bypass with negative `take`","id":"CVE-2026-63421","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"OpenImageIO OpenEXR plugin partial edge tile heap out-of-bounds write","id":"CVE-2026-63422"},"packages":[{"ecosystem":"npm","fixed":["6.5.3"],"introduced":["0"],"last_affected":[],"package":"@keystone-6/core","purl":null,"source":"GHSA-cqmq-8755-7xvh"},{"ecosystem":"npm","fixed":["6.5.3"],"introduced":["0"],"last_affected":[],"package":"@keystone-6/core","purl":"pkg:npm/%40keystone-6/core","source":"GHSA-cqmq-8755-7xvh"}],"prev":{"headline":"OpenImageIO: PSD RawColor indexed image out-of-bounds read in `interleave_row`","id":"CVE-2026-63420"},"products":["keystone"],"published":"2026-08-21","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-08-26","vendors":["keystonejs"]},"summary":"Attackers can bypass GraphQL take limits using negative values to retrieve excessive records, potentially causing resource exhaustion.","url":"https://insights.sbomify.com/CVE-2026-63421/"}