Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

@keystone-6/core's NODE_ENV defaults to development with esbuild

CVE-2022-39382GHSA-25mx-2mxm-6343

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@keystone-6/core 3.0.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2022-39382: 2.06% estimated exploitation activity in the next 30 days; percentile 81.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact @keystone-6/core@3.0.0 || 3.0.1 users that use NODEENV in their own code (not dependencies) to trigger security-sensitive functionality in a production build are vulnerable to NODEENV being inlined to "development" for user code. If your dependencies use NODEENV to trigger particular behaviours (optimisations, security or otherwise), they should still respect your environment's configured NODEENV variable and thereby be unaffected. If you do not use NODEENV in your own code to trigger security-sensitive functionality, you are not impacted by this vulnerability. An example of code that would be affected, might be the following: Technical Description The problem comes from esbuild defaulting NODEENV to "development" when a platform configuration is undefined. You can read about why esbuild has that behaviour in their documentation, but the result for Keystone users is that user Typescript was compiled, and had inlined NODEENV to the constant "development". Your application's…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-25mx-2mxm-6343

  2. Revision 1 · created ·

    Published from osv record GHSA-25mx-2mxm-6343

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-39382

Advisory: @keystone-6/core's NODE_ENV defaults to development with esbuild
IDs: CVE-2022-39382, GHSA-25mx-2mxm-6343
Record: https://patchnext.com/advisories/cve-2022-39382 (revision 2, source checked 26 Oct 2026, 12:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @keystone-6/core 3.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @keystone-6/core: affected >= 3.0.0, < 3.0.2; fixed in 3.0.2

## Suggested inspection (read-only)
- `npm ls @keystone-6/core --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @keystone-6/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-25mx-2mxm-6343 (OSV record GHSA-25mx-2mxm-6343 lists affected ranges: npm @keystone-6/core >=3.0.0 <3.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-25mx-2mxm-6343 (GitHub-reviewed advisory GHSA-25mx-2mxm-6343 lists affected ranges: npm @keystone-6/core >=3.0.0 <3.0.2)

Commands are suggestions: review each one before running it.

Loading voting…