dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-11417

HIGH · 7.3 CVSS v3.1 Published 2026-06-10
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

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 local bundling pipeline in aws-cdk-lib before 2.245.0 (2.246.0 on Windows) might allow an actor who controls the value of one or more bundling properties (externalModules, define, loader, inject, or esbuildArgs) to execute arbitrary commands on the host running the CDK toolchain via injected shell metacharacters. This issue requires the threat actor to control the value of one or more of the affected bundling properties in the CDK application. To remediate this issue, users should upgrade to aws-cdk-lib 2.245.0 (2.246.0 on Windows) or later.

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

OS command injection vulnerability in aws-cdk-lib's NodejsFunction bundling pipeline. When specific bundling properties (externalModules, define, loader, inject, or esbuildArgs) contain shell metacharacters, they can be executed as arbitrary commands on the host system. This requires an attacker to control these property values in the CDK application configuration.

MitigationUpgrade aws-cdk-lib to version 2.245.0 (or 2.246.0 on Windows) or later. Audit CDK applications for any use of the affected bundling properties with user-controlled or untrusted input values.

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. Locate NodejsFunction usage in your CDK application
    Search your codebase for imports of 'aws-cdk-lib' and usage of 'NodejsFunction' construct. Review all CDK stacks that instantiate NodejsFunction.
    Affected if NodejsFunction is used in your CDK application code
  2. Identify configured bundling properties
    Examine each NodejsFunction instantiation for the following properties: externalModules, define, loader, inject, or esbuildArgs. These are passed via the 'bundling' option object.
    Affected if Any of these bundling properties are configured in your NodejsFunction definitions
  3. Inspect property values for shell metacharacters
    Review the values assigned to externalModules, define, loader, inject, and esbuildArgs. Look for characters like ; | & $ ` ( ) { } [ ] < > " ' \n \r or other shell metacharacters that could enable command injection.
    Affected if Any bundling property value contains shell metacharacters or comes from untrusted/user-controlled input
  4. Check for user-controlled or dynamic input sources
    Trace where the bundling property values originate. Determine if they come from environment variables, user config files, HTTP requests, databases, or other external sources that could be influenced by an attacker.
    Affected if Bundling property values derive from external or untrusted input sources
  5. Verify aws-cdk-lib version
    Check your package.json, package-lock.json, or run 'npm list aws-cdk-lib' to determine the installed version of aws-cdk-lib.
    Affected if The installed version is earlier than 2.245.0 (or earlier than 2.246.0 on Windows)

You are affected if your CDK application uses NodejsFunction with any of the bundling properties (externalModules, define, loader, inject, esbuildArgs) that contain shell metacharacters and your aws-cdk-lib version is below 2.245.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 version 2.245.0 (or 2.246.0 on Windows) or later. Audit CDK applications for any use of the affected bundling properties with user-controlled or untrusted input values.

Recommended fix High confidence

aws-cdk-lib 2.245.0 (or 2.246.0 on Windows)

  1. Check the current aws-cdk-lib version in use (e.g., in package.json, package-lock.json, or your lock file)
  2. Update aws-cdk-lib to version 2.245.0 or later using your package manager (e.g., npm install aws-cdk-lib@^2.245.0, or yarn upgrade aws-cdk-lib@^2.245.0, or pnpm update aws-cdk-lib)
  3. If running on Windows, use version 2.246.0 or later
  4. After updating, rebuild and redeploy your CDK stacks to verify the application functions correctly
Caveat Review the aws-cdk-lib release notes between your current version and 2.245.0 for any breaking changes that may affect your CDK applications

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11417 — 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-11417 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