Skip to main content
VulnerabilityPublished Updated

CVE-2026-63421: keystonejs keystone · Improper Input Validation

Affects keystonejs keystoneSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 6.5.3 soon.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade keystonejs keystone to 6.5.3.

Affected software

ProductAffectedFixed in
keystonejskeystoneAffected
  • <6.5.3
Fixed in
  • 6.5.3

AI-suggested

Upgrade KeystoneJS to version 6.5.3 or later, where this vulnerability is fixed. No other mitigations are specified. Patch status is confirmed as an official fix in version 6.5.3.

Description

CVE-2026-63421 is an improper input validation vulnerability in KeystoneJS prior to version 6.5.3. It allows a remote unauthenticated GraphQL client to provide a negative 'take' argument with a magnitude exceeding the configured maximum, bypassing intended query limits. This can lead to returning more records than intended, potentially exhausting service resources. The issue affects the findMany resolver and relationship queries. The vulnerability is fixed in KeystoneJS version 6.5.3.

References

Community reviews

Loading reviews…