Summary

Keystone vulnerable to `graphql.maxTake` bypass with negative `take`

Severity

high

CVSS

7.5

EPSS

0.7% (p52)

CWE

CWE-20, CWE-480

Also known as

GHSA-cqmq-8755-7xvh

Published

2026-08-21

Updated

2026-08-21

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 advisories

• CVE-2026-96620 — critical · PyPI/claude-agent-sdk
• CVE-2026-107726 — critical · Maven/com.hazelcast:hazelcast
• CVE-2026-55068 — critical · Go/github.com/free5gc/free5gc
• CVE-2026-54133 — critical · Packagist/mtdowling/jmespath.php
• GHSA-rjg6-39jm-rgg4 — critical · npm/@better-auth/scim
• CVE-2026-53713 — critical · Go/github.com/envoyproxy/gateway
• CVE-2026-53513 — critical · npm/@better-auth/sso
• CVE-2026-48769 — critical · Go/github.com/lxc/incus/v7/cmd/incusd

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Summarize with AI

ChatGPTClaudePerplexity