AWS CDK 2.274.0 Fixes Redshift Custom-Resource SQL Injection
Tech GuruQuick Answer
AWS bulletin 2026-151-AWS fixes CVE-2026-115418 in @aws-cdk/aws-redshift-alpha. Upgrade to 2.274.0-alpha.0 or later, review existing grants to PUBLIC, validate deployment roles and generated SQL, and retain evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory CDK applications and pipelines using @aws-cdk/aws-redshift-alpha, exact package versions, construct inputs, deployment roles, Redshift clusters, forks, owners, and recent deployments. Confirm whether an actor outside the trusted developer boundary could influence the affected construct properties; do not infer exposure from Redshift or CDK use alone. Upgrade to @aws-cdk/aws-redshift-alpha 2.274.0-alpha.0 or later, patch maintained forks, and review existing table grants to PUBLIC as AWS directs. Confirm lockfiles and deployed code, inspect generated SQL and Redshift grants, test representative deployments under least privilege, review relevant pipeline activity, and retain package and change evidence.
Last verified: 2026-10-27 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | AWS CDK @aws-cdk/aws-redshift-alpha database-query custom resource handlers |
|---|---|
| Advisory | 2026-151-AWS |
| CVE | CVE-2026-115418 |
| Authoritative release date | 2026-10-26 16:30:00 UTC |
| Authority revision date | 2026-10-26 18:13:10.227 UTC |
| Affected versions | @aws-cdk/aws-redshift-alpha releases before 2.274.0-alpha.0 when an actor can influence construct property values such as user names, comments, or passwords. |
| Fixed version | @aws-cdk/aws-redshift-alpha 2.274.0-alpha.0 or later |
| CVSS base score | 7.0 (CVSS v4.0); 7.3 (CVSS v3.1) |
| CVSS severity | High |
| Exploitation status | AWS does not state that this issue is being maliciously exploited.; no exploitation claim is inferred. |
What Changed
AWS fixed SQL injection that can cause deployment-time statements to run with Amazon Redshift superuser privileges, including grants to all cluster users.
What To Validate Now
- Inventory. Inventory CDK applications and pipelines using @aws-cdk/aws-redshift-alpha, exact package versions, construct inputs, deployment roles, Redshift clusters, forks, owners, and recent deployments.
- Establish applicability. Confirm whether an actor outside the trusted developer boundary could influence the affected construct properties; do not infer exposure from Redshift or CDK use alone.
- Remediate. Upgrade to @aws-cdk/aws-redshift-alpha 2.274.0-alpha.0 or later, patch maintained forks, and review existing table grants to PUBLIC as AWS directs.
- Validate. Confirm lockfiles and deployed code, inspect generated SQL and Redshift grants, test representative deployments under least privilege, review relevant pipeline activity, and retain package and change evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
The vulnerable module is experimental, but generated statements can run with Redshift superuser privileges. Trusted-input controls are interim risk reduction and do not replace the fixed package.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
