3.1
CWE
203 200
EPSS
0.027%
Advisory Published
CVE Published
Updated

CVE-2025-46720: Keystone has an unintended `isFilterable` bypass that can be used as an oracle to match hidden fields

First published: Mon May 05 2025(Updated: )

# 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: false` statically 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: true` for relevant fields, which implicitly removes filtering by these fields your GraphQL schema - Deny `update` and `delete` operations for the relevant **lists** completely (e.g `list({ access: { operation: { update: false, delete: false } }, ... })`)

Credit: security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
Keystone<6.5.0
npm/@keystone-6/core<=6.4.0
6.5.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2025-46720?

    CVE-2025-46720 has been classified as a moderate severity vulnerability.

  • How do I fix CVE-2025-46720?

    To mitigate CVE-2025-46720, upgrade to Keystone version 6.5.0 or later.

  • What type of vulnerability is CVE-2025-46720?

    CVE-2025-46720 is an access control vulnerability affecting the Keystone CMS.

  • Which versions of Keystone are affected by CVE-2025-46720?

    CVE-2025-46720 affects Keystone versions prior to 6.5.0.

  • How does CVE-2025-46720 impact Keystone users?

    CVE-2025-46720 allows unauthorized access to sensitive data through bypassed filters in update and delete mutations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203