CVE-2025-46720: @keystone 6/core Keystone Has An Unintended `isFilterable` Vulnerability
LOWCVE-2025-46720 is a LOW (CVSS 3.1) keystone has an unintended `isfilterable` vulnerability (CWE-203: Observable Discrepancy) affecting @keystone 6/core libraries in the npm ecosystem. The issue involves keystone has an unintended `isfilterable` bypass that can be used as an oracle to match hidden fields. Remediation is available by upgrading affected packages to version 6.5.0.
CVE-2025-46720 at a Glance
Security Impact
CVSS: 3.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2025-46720
To remediate this vulnerability, upgrade all affected @keystone 6/core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @keystone-6/core@6.5.0Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @keystone-6/coreHow to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2025-46720, inspect your project dependencies using npm:
npm ls @keystone-6/coreAnalyze the terminal output to locate any version of @keystone 6/core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.5.0), your application is affected.
Note: The npm ls @keystone-6/core command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-203: Observable Discrepancy, where the product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor. In @keystone 6/core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-46720 Affected @keystone 6/core Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@keystone-6/core
|
npm |
< 6.5.0
|
6.5.0
|
References
Frequently Asked Questions
What is CVE-2025-46720?
Which @keystone 6/core versions are affected?
What version fixes CVE-2025-46720?
Is @keystone-6/core affected?
What is the CVSS score of CVE-2025-46720?
What CWE is associated with CVE-2025-46720?
How can I check npm dependencies for CVE-2025-46720?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-hg9m-67mm-7pg3",
"modified" : "2025-05-05T22:06:50Z",
"published" : "2025-05-05T18:51:34Z",
"aliases" : [ "CVE-2025-46720" ],
"summary" : "Keystone has an unintended `isFilterable` bypass that can be used as an oracle to match hidden fields",
"details" : "# Summary \n`{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.\n\nSpecifically, 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.\n\n# Impact \nThis 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.\n\nThis 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)\n\n# Patches \nThis issue has been patched in `@keystone-6/core` version 6.5.0.\n\n# Workarounds \nTo mitigate this issue in older versions where patching is not a viable pathway.\n\n- Set `isFilterable: false` statically for relevant fields to prevent filtering by them earlier in the access control pipeline (that is, don't use functions)\n- Set `{field}.graphql.omit.read: true` for relevant fields, which implicitly removes filtering by these fields your GraphQL schema\n- Deny `update` and `delete` operations for the relevant **lists** completely (e.g `list({ access: { operation: { update: false, delete: false } }, ... })`)",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@keystone-6/core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "6.5.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 6.4.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/keystonejs/keystone/security/advisories/GHSA-hg9m-67mm-7pg3"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-46720"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/keystonejs/keystone"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-200", "CWE-203" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2025-05-05T18:51:34Z",
"nvd_published_at" : "2025-05-05T19:15:57Z"
}
}