cve.bz

CVE-2026-63421 keystonejs keystone: Use of Incorrect Operator

7.5 highEPSS 0.7%Fix available

High (7.5) in keystonejs keystone. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in @keystone-6/core 6.5.3.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-08-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-480 Use of Incorrect Operator
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @keystone-6/core (npm): fixed in 6.5.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-63421 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63421?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63421?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63421 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-63421

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-63421](https://cve.bz/cve/badge/CVE-2026-63421.svg)](https://cve.bz/cve/CVE-2026-63421)

HTML:

<a href="https://cve.bz/cve/CVE-2026-63421"><img src="https://cve.bz/cve/badge/CVE-2026-63421.svg" alt="CVE-2026-63421"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
keystonejs keystone< 6.5.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-cqmq-8755-7xvhnpm@keystone-6/core<6.5.36.5.3

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON