Quick answers
- Is CVE-2026-33326 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33326 being exploited in the wild.
- How severe is CVE-2026-33326?
- Low severity, with a CVSS score of 3.1, published 19 March 2026.
- Which products and versions are affected?
- @keystone-6/core (npm) SEMVER:introduced=0,fixed=6.5.2.
- Is there a fix for CVE-2026-33326?
- Yes. @keystone-6/core (npm): upgrade to 6.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-33326 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-33326?
- Check whether you run @keystone-6/core (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @keystone-6/core (npm): upgrade to 6.5.2 or later
npm install @keystone-6/core@6.5.2
Technical details
The vulnerability is an authorization bypass (CWE-863) in the findMany GraphQL query handler. The cursor parameter accepts a UniqueWhere input type that was not subjected to the same isFilterable access control checks that were added to update and delete mutations in the previous CVE-2025-46720 fix. An authenticated attacker (PR:L) can craft findMany queries with cursor values that reference protected fields to confirm the existence of records without having permission to filter by those fields. This is a network-reachable attack with no user interaction required. The vulnerability has been patched in version 6.5.2; prior versions up to 6.5.1 are affected.
Affected products
- KeystoneJS @keystone-6/core <= 6.5.1
Identifiers
- CVE-2026-33326
- GHSA-cgcg-q9jh-5pr2
Timeline
- 2026-03-19: disclosed
- 2026-03-19: patched: version 6.5.2