Keystone vulnerable to `graphql.maxTake` bypass with negative `take`
GHSA-cqmq-8755-7xvh · CVE-2026-63421
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
Summary
The value of graphql.maxTake can be bypassed by providing a negative input.
This can be used to exceed the developer's intended graphql.maxTake value, allowing queries to return results in excess of the graphql.maxTake value set.
Impact
This affects any project relying on graphql.maxTake to bound the number of items returned per query.
Patches
This issue has been patched in @keystone-6/core version 6.5.3.
If you cannot patch, you can workaround this by restricting take input values in your GraphQL queries to the bounded value, or by blocking negative values.
Credit
This issue was found by Haxset's Security Scanner and validated by their team.
References
- WEB https://github.com/keystonejs/keystone/security/advisories/GHSA-cqmq-8755-7xvh
- WEB https://github.com/keystonejs/keystone/pull/9859
- WEB https://github.com/keystonejs/keystone/commit/9fb88b246950ce4de754a43fe6416f20403577b1
- PACKAGE https://github.com/keystonejs/keystone
- WEB https://github.com/keystonejs/keystone/releases/tag/@keystone-6/core@6.5.3
Ready to move
Start Securing
Free, no credit card | First findings in minutes