Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.0amended

aws-cdk-lib: OS Command Injection in NodejsFunction Docker Bundling

CVE-2026-13760GHSA-vcrf-j523-4mrf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (aws-cdk-lib 2.260.0), 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 4.0
7.0 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-13760: 1.16% estimated exploitation activity in the next 30 days; percentile 67.15 (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.

Summary AWS CDK (aws-cdk-lib) is an open-source framework for defining cloud infrastructure in code and provisioning it through AWS CloudFormation. OS command injection issue in the NodejsFunction Docker bundling pipeline in aws-cdk-lib before 2.260.0 that might allow an actor who controls dependency version strings in a project's package.json file to execute arbitrary commands on the host running the CDK toolchain via injected shell metacharacters in the OsCommand helper. This issue requires the actor to control the content of a package.json dependency version string that is processed during Docker-based bundling with nodeModules specified. Impact During Docker-based Lambda bundling, when the nodeModules option is specified, NodejsFunction assembled a shell command string, including file-operation commands generated by an internal OsCommand helper, from the version strings of the modules listed in nodeModules, and executed it via a shell (bash -c) inside the bundling container.…

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

    Amended from ghsa record GHSA-vcrf-j523-4mrf

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-vcrf-j523-4mrf

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-2026-13760

Advisory: aws-cdk-lib: OS Command Injection in NodejsFunction Docker Bundling
IDs: CVE-2026-13760, GHSA-vcrf-j523-4mrf
Record: https://patchnext.com/advisories/cve-2026-13760 (revision 3, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: aws-cdk-lib 2.260.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm aws-cdk-lib: affected < 2.260.0; fixed in 2.260.0

## Suggested inspection (read-only)
- `npm ls aws-cdk-lib --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 aws-cdk-lib.
- 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-vcrf-j523-4mrf (OSV record GHSA-vcrf-j523-4mrf lists affected ranges: npm aws-cdk-lib >=0 <2.260.0 (fixed))
- Verified: https://github.com/advisories/GHSA-vcrf-j523-4mrf (GitHub-reviewed advisory GHSA-vcrf-j523-4mrf lists affected ranges: npm aws-cdk-lib >=0 <2.260.0)

Commands are suggestions: review each one before running it.

Loading voting…