AWS CDK Redshift CVE-2026-115418

Exploitation requires that the deployment use the @aws-cdk/aws-redshift-alpha module's database-query custom resource handlers (which manage Redshift users and grants) at a version before 2.274.0-alpha.0, AND that an attacker can influence the construct property values that feed those handlers - specifically the user name, comment, or password fields - where crafted input is interpolated into SQL. Limiting factors: the CVSS vector is local (AV:L) with low privileges (PR:L) and requires active user interaction (UI:A), i.e. a CDK stack deployment must occur with the attacker-influenced values; it is not remotely reachable against a running service. Deployments that only use trusted, static property values are not realistically exposed. Remediation is to upgrade to 2.274.0-alpha.0 or later and review existing table grants to PUBLIC.

This is a genuine but conditional risk rather than a drop-everything emergency. The vendor-supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:A) describes a local, low-privilege attack that still requires active user interaction, not remote unauthenticated compromise - so despite the HIGH vulnerable-system impact (VC:H/VI:H/VA:H) the base score lands at 7.0 (High, not Critical). The vuln.today decision label is 'this_week', consistent with a patch-available, moderate-urgency item. No EPSS score, no CISA KEV listing, and no PoC reference are present in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The practical gate is the PR:L / UI:A requirement: an attacker must be able to influence the construct property values (user names, comments, or passwords) consumed by the aws-redshift-alpha database-query custom resource handlers AND have that CDK stack deployed. That makes this a supply-chain / untrusted-input-in-IaC concern (e.g. property values sourced from external or multi-tenant input) rather than a broadly automatable internet-facing flaw. Note the module is an 'alpha' (experimental) CDK package, which narrows the real-world exposed population. Net: prioritize patching where Redshift users/grants are provisioned via this module from any externally influenced values, but it does not carry KEV/EPSS signals of mass exploitation.

An application or pipeline provisions Amazon Redshift users via the @aws-cdk/aws-redshift-alpha database-query custom resource, deriving a user name, comment, or password from externally influenced input. An attacker who can shape that property value embeds SQL into it, and when the CDK stack is deployed the custom resource handler executes the injected statements with Redshift superuser privileges - for example granting all cluster users access to data. No public exploit code is identified in the available sources.