CVE-2026-33326VulnerabilityPublished 24 Mar 2026

CVE-2026-33326: keystonejs keystone · Incorrect Authorization

Affects keystonejs keystoneSource CVE Database V5

Mentioned vulnerabilities

CVE-2025-46720

Not known to be exploited · CVSS 4.3 Medium : upgrade to 6.5.2 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.5.2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade keystone and keystonejs/keystone to 6.5.2.

Affected software

Product	Affected	Fixed in
keystonejskeystone	Affected <6.5.2	Fixed in 6.5.2
GitHubkeystonejs/keystone`pkg:github/keystonejs/keystone`Other threats	Affected <6.5.2	Fixed in 6.5.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should upgrade all KeystoneJS installations to version 6.5.2 or later, where the issue has been fully patched. In addition to upgrading, administrators should audit access control policies to ensure that field-level permissions are correctly configured and enforced. Implementing strict privilege separation and minimizing user privileges can reduce the risk of exploitation. Monitoring and logging of findMany queries, especially those using cursor parameters, can help detect suspicious activity indicative of exploitation attempts. If immediate upgrading is not feasible, consider implementing network-level access controls to restrict access to KeystoneJS management interfaces and APIs to trusted users only. Regularly review and apply security advisories from KeystoneJS and related dependencies to stay ahead of emerging vulnerabilities.

Description

CVE-2026-33326 is a medium severity vulnerability in KeystoneJS versions prior to 6.5.2 that allows bypassing access control on the isFilterable field during findMany queries by exploiting the cursor parameter. This flaw enables attackers with limited privileges to confirm the existence of records based on protected field values, potentially leaking sensitive information. The vulnerability stems from incomplete patching after a previous related issue (CVE-2025-46720) where update and delete mutations were fixed but the cursor parameter in findMany queries was overlooked. Exploitation requires network access and low privileges but no user interaction. The issue has been fixed in KeystoneJS version 6.5.2. Organizations using vulnerable versions should upgrade promptly to prevent unauthorized data exposure.

Impact

The primary impact of this vulnerability is unauthorized information disclosure. Attackers with limited privileges can leverage the cursor parameter in findMany queries to confirm the existence of records containing protected field values, potentially exposing sensitive or confidential data. While the vulnerability does not allow modification or deletion of data, the ability to enumerate protected records can aid in reconnaissance and facilitate further targeted attacks. Organizations using KeystoneJS in environments where sensitive data is managed may face increased risk of data leakage, which could lead to compliance violations, reputational damage, and loss of customer trust. Since the vulnerability requires some level of privilege, the risk is somewhat mitigated but remains significant in multi-tenant or shared environments where privilege boundaries are critical. The lack of known exploits suggests limited active exploitation, but the vulnerability's presence in widely used versions means many deployments could be affected if not patched.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/keystonejs/keystone/security/advisories/GHSA-cgcg-q9jh-5pr2 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Mar 2026, 20:22 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats