AWS CDK CodePipeline: trusted entities are too broad

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.8 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The AWS Cloud Development Kit (CDK) is an open-source framework for defining cloud infrastructure using code. Users use it to create their own applications, which are converted to AWS CloudFormation templates during deployment to a user's AWS account. AWS CDK contains pre-built components called "constructs," which are higher-level abstractions providing defaults and best practices. This approach enables developers to use familiar programming languages to define complex cloud infrastructure more efficiently than writing raw CloudFormation templates. The AWS CodePipeline construct deploys CodePipeline, a managed service that orchestrates software release processes through a series of stages, each comprising one or more actions executed by CodePipeline. To perform these actions, CodePipeline assumes IAM roles with permissions necessary for each step, allowing it to interact with AWS services and resources on behalf of the user. An issue exists where, when using CDK to create a…

Published by the source

24 Mar 2025, 15:45 UTC

Last modified by the source

10 Apr 2025, 02:03 UTC

Source last checked

26 Oct 2026, 12:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5pq3-h73f-66hr

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5pq3-h73f-66hr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-5pq3-h73f-66hr

Advisory: AWS CDK CodePipeline: trusted entities are too broad
IDs: GHSA-5pq3-h73f-66hr
Record: https://patchnext.com/advisories/ghsa-5pq3-h73f-66hr (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: aws-cdk-lib 2.189.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm aws-cdk-lib: affected < 2.189.0; fixed in 2.189.0

## Suggested inspection (read-only)
- `npm ls aws-cdk-lib --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on aws-cdk-lib.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5pq3-h73f-66hr (OSV record GHSA-5pq3-h73f-66hr lists affected ranges: npm aws-cdk-lib >=0 <2.189.0 (fixed))
- Verified: https://github.com/advisories/GHSA-5pq3-h73f-66hr (GitHub-reviewed advisory GHSA-5pq3-h73f-66hr lists affected ranges: npm aws-cdk-lib >=0 <2.189.0)

Commands are suggestions: review each one before running it.