CVE-2026-33326: medium-severity vulnerability in keystonejs keystone
@keystone-6/core: `isFilterable` bypass via `cursor` parameter in findMany
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.3epss 0.3%
Keystone is a content management system for Node.js. Prior to version 6.5.2, {field}.isFilterable access control can be bypassed in findMany queries by passing a cursor. This can be used to confirm the existence of records by protected field values. The fix for CVE-2025-46720 (field-level isFilterable bypass for update and delete mutations) added checks to the where parameter in update and delete mutations however the cursor parameter in findMany was not patched and accepts the same UniqueWhere input type. This issue has been patched in version 6.5.2.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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-2026-63421HIGHKeystone: `graphql.maxTake` bypass with negative `take`EPSS 0.7%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%