---
id: "GHSA-h6j4-qpp7-q28p"
kind: "vulnerability"
aliases: ["GHSA-h6j4-qpp7-q28p"]
title: "CVE-2026-107608: Improper link resolution in asset bundling output handling in aws-cdk-lib"
severity: "medium"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["aws", "aws-cdk", "infrastructure-as-code", "lab-disclosure", "package", "python", "typescript"]
not_affected_if: ["no-docker-bundling", "trusted-bundling-images"]
published_at: null
first_seen_at: "2026-10-24T19:28:16+00:00"
updated_at: "2026-10-26T00:58:05+00:00"
sources: [{"source": "lab", "url": "https://aws.amazon.com/security/security-bulletins/rss/2026-131-aws/", "first_seen_at": "2026-10-24T19:28:16+00:00"}]
---

# CVE-2026-107608: Improper link resolution in asset bundling output handling in aws-cdk-lib

When aws-cdk-lib bundles an asset with a Docker file, a malicious Docker build can insert symlinks into the bundling output that were never declared as inputs. Those links can point at files outside the bundle, so the synthesized output may carry data the project did not intend to deploy.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `npm ls aws-cdk-lib` (or check the lockfile) to find the installed `aws-cdk-lib` version.
- Review Dockerfiles and bundling images used by `Code.fromAsset` or `DockerImage` bundling and confirm they come from trusted sources.

## Fix

- Upgrade `aws-cdk-lib` to `2.267.0` or later.
- Patch any forked or derivative CDK code as the bulletin recommends.
- Until upgraded, audit Docker bundling containers and their dependencies to confirm no untrusted code runs inside them.

## Mitigated for you by

- Team (workaround): covers Docker-based asset bundling in aws-cdk-lib before 2.267.0, by confirming that no untrusted code executes inside the bundling containers Limits: Does not fix the symlink insertion itself; the document states it only reduces the possibility of unexpected information being exposed Still: Audit all Docker bundling containers and their dependencies to confirm no untrusted code executes in the bundling environment, and upgrade to aws-cdk-lib 2.267.0 https://aws.amazon.com/security/security-bulletins/rss/2026-131-aws/
- Team (workaround): covers Reduces the chance of unexpected information being exposed through Docker bundling containers by auditing them and their dependencies. Limits: none stated Still: Audit all Docker bundling containers and their dependencies to confirm that no untrusted code executes inside the configured bundling environment, until aws-cdk-lib 2.267.0 can be installed. https://aws.amazon.com/security/security-bulletins/rss/2026-131-aws/

## Timeline

- 2026-10-24T19:28:16+00:00 lab https://aws.amazon.com/security/security-bulletins/rss/2026-131-aws/ — AWS: CVE-2026-107608: Improper link resolution in asset bundling output handling in aws-cdk-lib

## Documents

- [advisory] AWS: CVE-2026-107608: Improper link resolution in asset bundling output handling in aws-cdk-lib https://aws.amazon.com/security/security-bulletins/rss/2026-131-aws/

## From the sources

CVE-2026-107608: Improper link resolution in asset bundling output handling in aws-cdk-lib

### 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:

- CVE-2026-107608
- GHSA-h6j4-qpp7-q28p

 Please email aws-security@amazon.com with any security questions or concerns.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_