CVE-2022-39322: critical vulnerability in keystonejs keystone
@keystone-6/core vulnerable to field-level access-control bypass for multiselect field
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.1epss 1.5%
@keystone-6/core is a core package for Keystone 6, a content management system for Node.js. Starting with version 2.2.0 and prior to version 2.3.1, users who expected their `multiselect` fields to use the field-level access control - if configured - are vulnerable to their field-level access control not being used. List-level access control is not affected. Field-level access control for fields other than `multiselect` are not affected. Version 2.3.1 contains a fix for this issue. As a workaround, stop using the `multiselect` field.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected products
keystonejs · keystoneRelated CVEs — keystonejs keystone
In the same product, most dangerous first.
CVE-2022-39382CRITICALNODE_ENV in Keystone defaults to development with esbuildEPSS 2.1%CVE-2026-63421HIGHKeystone: `graphql.maxTake` bypass with negative `take`EPSS 0.7%CVE-2023-40027LOWConditionally missing authorization in @keystone-6/coreEPSS 0.6%CVE-2023-34247MEDIUM@keystone-6/auth Open Redirect vulnerabilityEPSS 0.4%CVE-2026-10802MEDIUMkeystonejs keystone GraphQL API Endpoint output-field.ts resource consumptionEPSS 0.3%CVE-2026-33326MEDIUM@keystone-6/core: `isFilterable` bypass via `cursor` parameter in findManyEPSS 0.3%