Summary
Keystone vulnerable to `graphql.maxTake` bypass with negative `take`
Advisory details
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
- https://github.com/advisories/GHSA-cqmq-8755-7xvh
- https://github.com/keystonejs/keystone/security/advisories/GHSA-cqmq-8755-7xvh
- https://github.com/keystonejs/keystone/pull/9859
- https://github.com/keystonejs/keystone/commit/9fb88b246950ce4de754a43fe6416f20403577b1
- https://github.com/keystonejs/keystone/releases/tag/@keystone-6/core@6.5.3
Related vulnerabilities
All Supply chain →- HIGHCVE-2026-75975
fast-uri vulnerable to server-side request forgery via malformed IPv6 normalization
- MEDIUMCVE-2026-18504
fastify vulnerable to schema validation bypass via root primitive coercion mismatch
- MEDIUMCVE-2026-73845
CKAN MCP Server: MQA server allowlist bypass via unanchored regex (`isValidMqaServer`)
- HIGHCVE-2026-59724
Socket.IO: Engine.IO WebTransport SID DoS
- HIGHCVE-2026-55212
Pimcore: Insufficient Permission Check on Class Definition Creation Endpoint Allows Privilege Escalation
- CRITICALCVE-2026-55068
free5GC NRF nnrf-nfm lacks NF Profile input validation — enables NF Registration Poisoning with arbitrary service endpoints