aws
aws-cdk
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at aws-cdk, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-13760 | 1 Jul 2026 | < 2.260.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-23206 | 17 Jan 2025 | < 2.177.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-45037 | 27 Aug 2024 | >= 2.142.0, < 2.148.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-35165 | 23 Jun 2023 | aws-cdk-lib >= 2.0.0, < 2.80.0; @aws-cdk/aws-eks >= 1.57.0, < 1.202.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.