Update dependency aws-cdk-lib to v2.260.0 [SECURITY]#6081
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.253.1→2.260.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
aws-cdk-lib: OS Command Injection in NodejsFunction Docker Bundling
CVE-2026-13760 / GHSA-vcrf-j523-4mrf
More information
Details
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.
Impacted versions:
< 2.260.0
Patches
This issue has been addressed in aws-cdk-lib version 2.260.0 (PR #38133). We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds
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 third-party constructs and dependencies that introduce them. Using local bundling instead of Docker-based bundling avoids the affected code path. Upgrading to a fixed version is the recommended remediation.
References
If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
Acknowledgement
We would like to thank the external researcher Mostafa Ashraf who reported this issue through the AWS Vulnerability Disclosure Program (HackerOne @kaporia) for collaborating on it through the coordinated vulnerability disclosure process.
Severity
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
aws/aws-cdk (aws-cdk-lib)
v2.260.0Compare Source
Features
Bug Fixes
Alpha modules (2.260.0-alpha.0)
v2.259.0Compare Source
⚠ BREAKING CHANGES
lambda:
Runtime.NODEJS_LATESTnow resolves tonodejs24.xin every region. Customers who pin to a concrete runtime (Runtime.NODEJS_22_X,useLatestRuntimeVersion: falseinaws-lambda-nodejs.NodejsFunction) are unaffected. ExistingAWS::Lambda::Functionresources synthesized withNODEJS_LATESTwill seeRuntime: nodejs22.x→Runtime: nodejs24.xon next deploy. Lambda accepts runtime updates in place.Customer-code compatibility — IMPORTANT: Node.js 24 removes support for callback-style asynchronous handlers (
(event, context, callback) => {...}) per the launch blog. Customers whose Lambda code still uses callback-based handlers will see runtime errors after the bump. Customers should migrate toasync (event, context) => {...}or pin toRuntime.NODEJS_22_Xexplicitly.Features
Bug Fixes
Reverts
Alpha modules (2.259.0-alpha.0)
v2.258.1Compare Source
Reverts
Alpha modules (2.258.1-alpha.0)
v2.258.0Compare Source
⚠ BREAKING CHANGES
Features
Bug Fixes
Alpha modules (2.258.0-alpha.0)
Features
Bug Fixes
v2.257.0Compare Source
⚠ BREAKING CHANGES
** L1 resources are automatically generated from public CloudFormation Resource Schemas. They are built to closely reflect the real state of CloudFormation. Sometimes these updates can contain changes that are incompatible with previous types, but more accurately reflect reality. In this release we have changed:
Features
Alpha modules (2.257.0-alpha.0)
v2.256.1Compare Source
Bug Fixes
Alpha modules (2.256.1-alpha.0)
v2.256.0Compare Source
Features
anyreturn types with specific interfaces inIPeermethods (#36637) (626e44d), closes #36636bucketNamePrefixandbucketNamespaceproperties (#37386) (997b003), closes #37760Bug Fixes
Alpha modules (2.256.0-alpha.0)
v2.255.0Compare Source
Features
PropertyMergeStrategys are now compatible with deferredBoxvalues (#37844) (ca4b722)Bug Fixes
Lazys use the Box API internally (#37889) (464fa3d)Alpha modules (2.255.0-alpha.0)
Features
aws-cdk-lib/aws-bedrockagentcoreand we recommend migrating to the stable versions (#37876) (00cf601)v2.254.0Compare Source
⚠ BREAKING CHANGES
aws-elasticache: AWS::ElastiCache::CacheCluster: Id attribute removed.
aws-sagemaker: AWS::SageMaker::Model: Id attribute removed.
aws-vpclattice: AWS::VpcLattice::AuthPolicy: State attribute enum values changed from ACTIVE|INACTIVE to Active|Inactive.
Features
PropertyMergeStrategynow supports array merge strategies (#37841) (701305d)Bug Fixes
Alpha modules (2.254.0-alpha.0)
Features
Bug Fixes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.