@keystone-6/core: isFilterable bypass via cursor parameter in findMany (CVE-2025-46720 incomplete fix)

Exploitation

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

CVSS

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

EPSS

• CVE-2026-33326: 0.27% estimated exploitation activity in the next 30 days; percentile 18.95 (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 findMany queries by passing a cursor. This can be used to confirm the existence of records by protected field values. The fix for CVE-2025-46720 (field-level isFilterable bypass for update and delete mutations) added checks to the where parameter in update and delete mutations however the cursor parameter in findMany was not patched and accepts the same UniqueWhere input type. Impact This affects any project relying on isFilterable behaviour (at the list or field level) to prevent external users from using the filtering of fields as a discovery mechanism. isFilterable access control using a function can be bypassed by using the cursor input. 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.2.…

Published by the source

19 Mar 2026, 18:37 UTC

Last modified by the source

27 Mar 2026, 22:03 UTC

Source last checked

26 Oct 2026, 12:47 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-cgcg-q9jh-5pr2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-cgcg-q9jh-5pr2

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

# Patch Next advisory brief: CVE-2026-33326

Advisory: @keystone-6/core: `isFilterable` bypass via `cursor` parameter in findMany (CVE-2025-46720 incomplete fix)
IDs: CVE-2026-33326, GHSA-cgcg-q9jh-5pr2
Record: https://patchnext.com/advisories/cve-2026-33326 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
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.2. A vendor fix does not mean a deployment is fixed.

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

## 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-cgcg-q9jh-5pr2 (OSV record GHSA-cgcg-q9jh-5pr2 lists affected ranges: npm @keystone-6/core >=0 <6.5.2 (fixed))
- Verified: https://github.com/advisories/GHSA-cgcg-q9jh-5pr2 (GitHub-reviewed advisory GHSA-cgcg-q9jh-5pr2 lists affected ranges: npm @keystone-6/core >=0 <=6.5.1)

Commands are suggestions: review each one before running it.