Live › vulnerability › CVE-2026-107608
Go to dashboardIn aws-cdk-lib before 2.267.0, a Dockerfile used for asset bundling could insert a symlinked file or directory into the bundling output without that symlink being declared as input. The symlink can point outside the bundle, so content from the build machine can be pulled into the deployed asset.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-24 19:28 UTC, 1h before NVD. All times on this page are UTC.
Teams that use aws-cdk-lib before 2.267.0 with Docker-based asset bundling, where the Dockerfile or the image contents are not fully trusted. Projects that only use CDK without Docker bundling, or that build assets only from code they fully control, face much less risk. Teams already on 2.267.0 or later are not affected.
No product ranges from the sources yet.
npx cdk --version or check aws-cdk-lib in package.json / package-lock.json against 2.267.0bundling: with image or a dockerfile in CDK constructs such as lambda.Code.fromAsset options) and review the Dockerfiles usedaws-cdk-lib to 2.267.0 or laterThe fix above is the answer. These hold the line until you can deploy it, and are the only option on lines that get no fix.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
CVE-2026-107608: Improper link resolution in asset bundling output handling in aws-cdk-lib
Bulletin ID: 2026-131-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/08/2026 12:30 PM PDT
Description:
AWS CDK is an open source framework that allows customers to build cloud infrastructure using their favorite programming language (Python, Typescript, C#, Go). That infrastructure is then able to be deployed with AWS CDK command line commands to AWS CloudFormation. We identified CVE-2026-107608, which is an issue where Docker files could be configured to insert symlinked files into the output of the AWS CDK asset bundling process when it was invoked with a Docker file. When bundling an asset using AWS CDK with a docker file, prior to 2.267.0, it was possible for a docker file to insert a symlinked file or directory into the output of asset bundling without the symlink having been provided as input to the bundling process.
Impacted versions: All aws-cdk-lib versions before 2.267.0
Resolution:
This issue has been addressed in aws-cdk-lib version 2.267.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds:
If you cannot immediately upgrade, you can reduce the possibility of streaming unexpected information by auditing all Docker bundling containers and their dependencies to confirm that no untrusted code executes inside the configured bundling environment.
References:
Please email [email protected] with any security questions or concerns.
This page as .md · .json · in your agent: get_signal("CVE-2026-107608")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.