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

> An attacker can exploit improper link resolution to publish sensitive host files as deployed assets, requiring an upgrade to the AWS CDK library.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026

## What is CVE-2026-107608?

CVE-2026-107608 is a medium-severity path traversal vulnerability in aws-cdk-lib, published on 8 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Improper link resolution before file access in the asset bundling output handling in AWS aws-cdk-lib before 2.267.0 might allow a context-dependent actor to cause files from the build host to be published as the deployed asset.

To remediate this issue, users should upgrade to version 2.267.0 or later.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-107608?


## How do I fix CVE-2026-107608?

No fix has been published for CVE-2026-107608 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-107608 being exploited?

There is no known exploitation of CVE-2026-107608 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107608 and fix it if it is affected.

What it is: CVE-2026-107608 is a medium-severity path traversal vulnerability in aws-cdk-lib, published on 8 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-107608 in the wild and no public exploit code.

Affected product: aws-cdk-lib. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107608/ (Markdown: https://insights.sbomify.com/CVE-2026-107608/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107608
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107608
- OSV: https://osv.dev/vulnerability/CVE-2026-107608

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107608/
Summaries are generated and may contain mistakes; the official description above is the record.