Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-13760 high CVSS 7.3

OS Command Injection in Amazon aws-cdk-lib (CVE-2026-13760)

Summary

OS command injection in Amazon aws-cdk-lib (CVE-2026-13760). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.260.0 or later.

Original description

The description as published by the source.

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. These version strings were interpolated without shell escaping, so values containing shell metacharacters could execute arbitrary commands inside the bundling container - which has read/write bind mounts to the host filesystem - with the privileges of the user running cdk synth, cdk deploy, or cdk diff. Leveraging this issue requires an actor to control a dependency version string for one of the listed modules - for example via an untrusted npm package referenced through nodeModules.

Imp…

Source: AWS Security Bulletins NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-13760 has been found in Amazon aws-cdk-lib.
Successful exploitation can lead to full system takeover. CVSS score: 7.3/10.
What to do: upgrade Amazon aws-cdk-lib to 2.260.0 or later.
If unsure, ask your IT team or search "Amazon aws-cdk-lib CVE-2026-13760" on the vendor's site.

CVE-2026-13760 (Amazon aws-cdk-lib) — CWE-78 / CVSS v3 7.3
Attack vector: local
Patched: 2.260.0 — apply immediately
Workaround: Ensure that the modules listed in the nodeModules bundling option - and the version strings declared for them in your project's package.json, as well as the versions of the corresponding installed packages - come only from trusted sources, and audit
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

OS command injection (CWE-78) exists in Amazon aws-cdk-lib.

📍 Affected scope

Check the vendor advisory for the affected versions of Amazon aws-cdk-lib.

🔥 Severity

Severity: High (CVSS 7.3/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.260.0.

🛡️ Workaround

Workaround: Ensure that the modules listed in the nodeModules bundling option - and the version strings declared for them in your project's package.json, as well as the versions of the corresponding installed packages - come only from trusted sources, and audit

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'aws-cdk-lib' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'aws-cdk-lib' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で aws-cdk-lib を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Ensure that the modules listed in the nodeModules bundling option - and the version strings declared for them in your project's package.json, as well as the versions of the corresponding installed packages - come only from trusted sources, and audit

    パッチが適用されるまでの応急処置として、Ensure that the modules listed in the nodeModules bundling option - and the version strings declared for them in your project's package.json, as well as the versions of the corresponding installed packages - come only from trusted sources, and audit を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade Amazon aws-cdk-lib to 2.260.0

    ステージング環境で 2.260.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm aws-cdk-lib
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.260.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details