CVE-2026-33326 @keystone-6/core: `isFilterable` bypass via `cursor` parameter in findMany

Medium 4.3 Published Updated

Attackers can bypass field-level access controls in Keystone CMS findMany queries to confirm the existence of records via protected field values.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-33326?

CVE-2026-33326 is a medium-severity missing authorization vulnerability in keystonejs keystone, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Keystone is a content management system for Node.js. Prior to version 6.5.2, {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. This issue has been patched in version 6.5.2.

Weakness: CWE-863

Which versions are affected by CVE-2026-33326?

2 open source packages ship an affected version, including @keystone-6/core. It affects 1 product.

PackageAffectedFixed in
@keystone-6/core npmAll versions6.5.2
@keystone-6/core npmAll versions6.5.2

Products include Keystonejs Keystone.

How do I fix CVE-2026-33326?

Upgrade @keystone-6/core to 6.5.2 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-33326 being exploited?

There is no known exploitation of CVE-2026-33326 in the wild and no public exploit code.

Sources

Also known as GHSA-cgcg-q9jh-5pr2.

Is CVE-2026-33326 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free