CVE-2026-63421: high-severity vulnerability in keystonejs keystone
Keystone: `graphql.maxTake` bypass with negative `take`
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.7%
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
keystonejs · keystoneRelated CVEs — keystonejs keystone
In the same product, most dangerous first.
CVE-2022-39382CRITICALNODE_ENV in Keystone defaults to development with esbuildEPSS 2.1%CVE-2022-39322CRITICAL@keystone-6/core vulnerable to field-level access-control bypass for multiselect fieldEPSS 1.5%CVE-2023-40027LOWConditionally missing authorization in @keystone-6/coreEPSS 0.6%CVE-2023-34247MEDIUM@keystone-6/auth Open Redirect vulnerabilityEPSS 0.4%CVE-2026-10802MEDIUMkeystonejs keystone GraphQL API Endpoint output-field.ts resource consumptionEPSS 0.3%CVE-2025-46720LOWKeystone has an unintended `isFilterable` bypass that can be used as an oracle to match hidden fieldsEPSS 0.3%