dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-13760

HIGH · 7.3 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OS command injection in the NodejsFunction Docker bundling pipeline (OsCommand helper) in AWS aws-cdk-lib on all platforms might allow a 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. To remediate this issue, users should upgrade to v2.260.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an OS command injection vulnerability in AWS CDK's NodejsFunction Docker bundling pipeline. An attacker who controls dependency version strings in a project's package.json can inject shell metacharacters through the OsCommand helper during Docker-based bundling with nodeModules, allowing arbitrary command execution on the host running the CDK toolchain.

MitigationUpgrade aws-cdk-lib to v2.260.0 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm AWS CDK is in use
    Check for cdk.json in the project root, or look for aws-cdk-lib in package.json dependencies
    Affected if The project does not use AWS CDK, this vulnerability does not apply
  2. Identify NodejsFunction usage
    Search CDK source files for imports from 'aws-cdk-lib' containing 'NodejsFunction' or search for new NodejsFunction( constructions
    Affected if NodejsFunction is not used in the CDK stack, this vulnerability does not apply
  3. Verify Docker bundling is enabled
    Examine NodejsFunction constructs for bundling property with nodeModules option set, and confirm Docker is configured as the bundling runtime
    Affected if NodejsFunction does not use Docker-based bundling with nodeModules, this vulnerability does not apply
  4. Check for untrusted dependency sources
    Review package.json for dependencies where version strings could be influenced by external/contributed sources, or check if the project pulls dependencies from untrusted registries
    Affected if No external or user-contributed dependencies are used, exploitation is not possible through this vector
  5. Determine aws-cdk-lib version
    Run 'npm list aws-cdk-lib' or check package-lock.json for the installed aws-cdk-lib version
    Affected if The installed version is earlier than v2.260.0, the environment is vulnerable to command injection through the described vector

A user is affected if their CDK project uses NodejsFunction with Docker bundling and nodeModules, pulls dependencies from sources controlled by untrusted parties, and runs an aws-cdk-lib version earlier than v2.260.0

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade aws-cdk-lib to v2.260.0 or later to remediate this vulnerability.

Recommended fix High confidence

v2.260.0

  1. Update the aws-cdk-lib version in your project's package.json to v2.260.0
  2. Run 'npm install' or 'yarn' to update the dependency to the fixed version
  3. Redeploy any CDK stacks that use NodejsFunction with Docker bundling to apply the fix
Caveat Minor version upgrade; minimal risk of breaking changes, but test in non-production first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13760 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data