Vulnerability in @keystone-6/core (CVE-2026-63421)
Summary
Vulnerability in @keystone-6/core (CVE-2026-63421). Risk of unauthorized operations or information disclosure. Exploitable via graphql.maxTake. Mitigation: upgrade to 6.5.3 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-63421 has been found in @keystone-6/core.
Attackers can target a specific entry point like graphql.maxTake over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade @keystone-6/core to 6.5.3 or later.
If unsure, ask your IT team or search "@keystone-6/core CVE-2026-63421" on the vendor's site.
CVE-2026-63421 (@keystone-6/core) — CWE-20 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: graphql.maxTake / take
Patched: 6.5.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in @keystone-6/core. Attackers reach the vulnerable code path via graphql.maxTake without authentication.
Check the vendor advisory for the affected versions of @keystone-6/core. Attack surface: graphql.maxTake / take.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 6.5.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@keystone-6/core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@keystone-6/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@keystone-6/coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @keystone-6/core to 6.5.3ステージング環境で 6.5.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。