CVE-2026-33326 | keystone up to 6.5.1 update/delete where authorization
VulDBArchived Mar 25, 2026✓ Full text saved
A vulnerability, which was classified as problematic , was found in keystone up to 6.5.1 . Affected by this vulnerability is the function update/delete . Executing a manipulation of the argument where can lead to incorrect authorization. This vulnerability appears as CVE-2026-33326 . The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-352859 · CVE-2026-33326 · GCVE-0-2026-33326
KEYSTONE UP TO 6.5.1 UPDATE/DELETE WHERE AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.2 $0-$5k 2.81
Summaryinfo
A vulnerability has been found in keystone up to 6.5.1 and classified as problematic. Affected by this issue is the function update/delete. The manipulation of the argument where leads to authorization. This vulnerability is traded as CVE-2026-33326. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Detailsinfo
A vulnerability was found in keystone up to 6.5.1 and classified as problematic. This issue affects the function update/delete. The manipulation of the argument where with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-863. 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. This allows attackers to bypass intended access restrictions. Impacted is confidentiality. The summary by CVE is:
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.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-33326 since 03/18/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 6.5.2 eliminates this vulnerability.
Productinfo
Name
keystone
Version
6.5.0
6.5.1
CPE 2.3info
🔒
🔒
CPE 2.2info
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (GitHub_M): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-863 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: keystone 6.5.2
Timelineinfo
03/18/2026 CVE reserved
03/24/2026 +6 days Advisory disclosed
03/24/2026 +0 days VulDB entry created
03/24/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-33326 (🔒)
GCVE (CVE): GCVE-0-2026-33326
GCVE (VulDB): GCVE-100-352859
Entryinfo
Created: 03/24/2026 20:56
Changes: 03/24/2026 20:56 (63)
Complete: 🔍
Cache ID: 99:19B:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸