CVE-2025-46720: Keystone has an unintended `isFilterable` bypass that can be used as an oracle to match hidden fields
Summary {field}.isFilterable access control can be bypassed in update and delete mutations by adding additional unique filters. These filters can be used as an oracle to probe the existence or value of otherwise unreadable fields. Specifically, when a mutation includes a where clause with multiple unique filters (e.g.
Published May 5, 2025
Affected packages
@keystone-6/core
- Ecosystem
- npm
- Affected
- <= 6.4.0
- Fixed in
- 6.5.0
- Check
npm ls @keystone-6/core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
{field}.isFilterable access control can be bypassed in update and delete mutations by adding additional unique filters. These filters can be used as an oracle to probe the existence or value of otherwise unreadable fields.
Specifically, when a mutation includes a where clause with multiple unique filters (e.g. id and email), Keystone will attempt to match records even if filtering by the latter fields would normally be rejected by field.isFilterable or list.defaultIsFilterable. This can allow malicious actors to infer the presence of a particular field value when a filter is successful in returning a result.
Impact
This affects any project relying on the default or dynamic isFilterable behaviour (at the list or field level) to prevent external users from using the filtering of fields as a discovery mechanism. While this access control is respected during findMany operations, it was not completely enforced during update and delete mutations when accepting more than one unique where values in filters.
This has no impact on projects using isFilterable: false or defaultIsFilterable: false for sensitive fields, or if you have otherwise omitted filtering by these fields from your GraphQL schema. (See workarounds)
Patches
This issue has been patched in @keystone-6/core version 6.5.0.
Workarounds
To mitigate this issue in older versions where patching is not a viable pathway.
- Set
isFilterable: falsestatically for relevant fields to prevent filtering by them earlier in the access control pipeline (that is, don't use functions) - Set
{field}.graphql.omit.read: truefor relevant fields, which implicitly removes filtering by these fields your GraphQL schema - Deny
updateanddeleteoperations for the relevant lists completely (e.glist({ access: { operation: { update: false, delete: false } }, ... }))
Credited to emmatown, dcousens.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-63421
Keystone vulnerable to `graphql.maxTake` bypass with negative `take`
high7.5Aug 21, 2026CVE-2026-10802
Keystone: GraphQL API Endpoint Lacks Query Depth Limits
low4.3No fixJun 4, 2026CVE-2026-33326
@keystone-6/core: `isFilterable` bypass via `cursor` parameter in findMany (CVE-2025-46720 incomplete fix)
medium4.3Mar 19, 2026
