CVE-2025-46720: 
JavaScript vulnerability analysis and mitigation

Keystone, a content management system for Node.js, was found to contain a security vulnerability (CVE-2025-46720) prior to version 6.5.0. The vulnerability involves a bypass of {field}.isFilterable access control in update and delete mutations through the use of additional unique filters. This vulnerability was discovered and disclosed on May 5, 2025, affecting all versions of @keystone-6/core before version 6.5.0 (GitHub Advisory, NVD).

The vulnerability occurs when a mutation includes a where clause with multiple unique filters (e.g., id and email). In such cases, Keystone attempts to match records even if filtering by the latter fields would normally be rejected by field.isFilterable or list.defaultIsFilterable. The vulnerability has been assigned a CVSS v3.1 Base Score of 3.1 (Low) with a vector string of CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N, indicating network vector attack with high complexity, requiring low privileges but no user interaction (GitHub Advisory).

The vulnerability affects projects that rely on the default or dynamic isFilterable behavior at either the list or field level to prevent external users from using field filtering as a discovery mechanism. While access control is properly enforced during findMany operations, it was not completely enforced during update and delete mutations when accepting multiple unique where values in filters. This can allow malicious actors to infer the presence of particular field values when a filter successfully returns a result (GitHub Advisory).

The issue has been patched in @keystone-6/core version 6.5.0. For older versions where patching is not viable, several workarounds are available: set isFilterable: false statically for relevant fields, set {field}.graphql.omit.read: true for relevant fields to remove them from the GraphQL schema, or deny update and delete operations for the relevant lists completely. Projects already using isFilterable: false or defaultIsFilterable: false for sensitive fields are not impacted (GitHub Advisory).