Quick answers
- Is CVE-2026-11417 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11417 being exploited in the wild.
- How severe is CVE-2026-11417?
- High severity, with a CVSS score of 7.3, published 10 June 2026.
- Which products and versions are affected?
- aws-cdk-lib (npm) < 2.246.0, SEMVER:introduced=0,fixed=2.246.0.
- Is there a fix for CVE-2026-11417?
- Yes. aws-cdk-lib (npm): upgrade to 2.246.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-11417 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-11417?
- Check whether you run AWS Cloud Development Kit, AWS Cloud Development Kit (CDK) Library or aws-cdk-lib (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- aws-cdk-lib (npm): upgrade to 2.246.0 or later
npm install aws-cdk-lib@2.246.0
Technical details
An OS command injection vulnerability exists in the `NodejsFunction` component of `aws-cdk-lib`. The root cause is the improper neutralization of shell metacharacters within bundling properties such as `externalModules`, `define`, `loader`, `inject`, and `esbuildArgs`. These values were interpolated into a command string and executed via a shell (`bash -c` or `cmd /c`) using `spawnSync`. An attacker who can control these properties—for example, through a malicious pull request or a compromised upstream dependency—can achieve arbitrary code execution with the privileges of the user running `cdk synth`, `cdk deploy`, or `cdk diff`. The vulnerability is fixed in version 2.245.0 (and 2.246.0 for Windows) by switching to array-based `spawnSync` calls that bypass shell interpretation.
Affected products
- AWS aws-cdk-lib < 2.245.0 (Linux/macOS), < 2.246.0 (Windows)
Identifiers
- CVE-2026-11417
- GHSA-999r-qq7v-r334
Timeline
- 2026-06-10: disclosed
- 2026-06-10: patched: Initial fix in 2.245.0; Windows regression fix in 2.246.0
- 2026-06-15: advisory