Keystone has an unintended isFilterable bypass that can be used as an oracle to match hidden fields

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2025-46720: 0.28% estimated exploitation activity in the next 30 days; percentile 20.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

5 May 2025, 18:51 UTC

Last modified by the source

5 May 2025, 22:06 UTC

Source last checked

26 Oct 2026, 12:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-hg9m-67mm-7pg3

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-hg9m-67mm-7pg3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-46720

Advisory: Keystone has an unintended `isFilterable` bypass that can be used as an oracle to match hidden fields
IDs: CVE-2025-46720, GHSA-hg9m-67mm-7pg3
Record: https://patchnext.com/advisories/cve-2025-46720 (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @keystone-6/core 6.5.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @keystone-6/core: affected <= 6.4.0; fixed in 6.5.0

## Suggested inspection (read-only)
- `npm ls @keystone-6/core --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @keystone-6/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hg9m-67mm-7pg3 (OSV record GHSA-hg9m-67mm-7pg3 lists affected ranges: npm @keystone-6/core >=0 <6.5.0 (fixed))
- Verified: https://github.com/advisories/GHSA-hg9m-67mm-7pg3 (GitHub-reviewed advisory GHSA-hg9m-67mm-7pg3 lists affected ranges: npm @keystone-6/core >=0 <=6.4.0)

Commands are suggestions: review each one before running it.