CVE-2022-39382
CWE-74Published: November 3, 2022· Updated: Jun 17, 2026
Official Description
Keystone is a headless CMS for Node.js — built with GraphQL and React.`@keystone-6/core@3.0.0 || 3.0.1` users that use `NODE_ENV` to trigger security-sensitive functionality in their production builds are vulnerable to `NODE_ENV` being inlined to `"development"` for user code, irrespective of what your environment variables. If you do not use `NODE_ENV` in your user code to trigger security-sensitive functionality, you are not impacted by this vulnerability. Any dependencies that use `NODE_ENV` to trigger particular behaviors (optimizations, security or otherwise) should still respect your environment's configured `NODE_ENV` variable. The application's dependencies, as found in `node_modules` (including `@keystone-6/core`), are typically not compiled as part of this process, and thus should be unaffected. We have tested this assumption by verifying that `NODE_ENV=production yarn keystone start` still uses secure cookies when using `statelessSessions`. This vulnerability has been fixed in @keystone-6/core@3.0.2, regression tests have been added for this vulnerability in #8063.
Risk Analysis
Keystone CMS versions 3.0.0 and 3.0.1 are vulnerable to an environment variable misconfiguration where NODE_ENV may be incorrectly inlined as development. This critical vulnerability could lead to security-sensitive functionality being exposed, though it is not currently listed in the KEV catalog.
There is no known public exploit for this vulnerability, but it is remotely exploitable with low complexity.
Users should upgrade to a patched version of Keystone and ensure environment variables are correctly configured.
Technical Analysis
CVE-2022-39382 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.
The vulnerability requires no privileges and no user interaction, making it a prime target for automated exploitation campaigns and worm-like propagation.
A successful exploit results in complete confidentiality breach (data exposure), full integrity compromise (data manipulation), availability disruption (denial of service), with a CVSS base score of 9.8.
CVSS v3.1 Vector Breakdown
Affected Vendors & Products
Exploit & PoC Resources
Official Patches & Advisories
All References (6)
Quick Facts
Related CVEs (CWE-74)
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2022-39382 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts