Skip to main content
CVE-2025-23206VulnerabilityPublished Updated

CVE-2025-23206: aws-cdk · Improper Verification of Cryptographic Signature

Affects aws-cdkSource CVE Database V5

0

Not known to be exploited · CVSS 1.8 Low : upgrade to 2.177.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
1.8Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.177.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade @aws-cdk/aws-cdk to 2.177.0.

Affected software

ProductAffectedFixed in
npm@aws-cdk/aws-cdkpkg:npm/@aws-cdk/aws-cdkOther threatsAffected
  • <2.177.0
Fixed in
  • 2.177.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should plan to upgrade their AWS CDK installations to version 2.177.0 or later as soon as it becomes available (expected February 22, 2025). After upgrading, they must explicitly enable the feature flag '@aws-cdk/aws-iam:oidcRejectUnauthorizedConnections' in their cdk.context.json or cdk.json configuration files to enforce strict TLS certificate validation during OIDC custom resource workflows. This approach balances security with backward compatibility. Organizations should audit their CDK applications to identify any reliance on unauthorized or self-signed OIDC providers and assess the risk of enabling strict TLS verification. Where possible, replace untrusted OIDC providers with properly certified endpoints. Additionally, implement monitoring and alerting on Lambda execution environments for unusual network activity that could indicate attempted MITM attacks. Since no workarounds exist, prioritizing the upgrade and configuration change is critical. Finally, incorporate this vulnerability into cloud infrastructure security assessments and DevSecOps pipelines to ensure ongoing compliance.

Description

The AWS Cloud Development Kit (AWS CDK) is an open-source software development framework to define cloud infrastructure in code and provision it through AWS CloudFormation. Users who use IAM OIDC custom resource provider package will download CA Thumbprints as part of the custom resource workflow. However, the current `tls.connect` method will always set `rejectUnauthorized: false` which is a potential security concern. CDK should follow the best practice and set `rejectUnauthorized: true`. However, this could be a breaking change for existing CDK applications and we should fix this with a feature flag. Note that this is marked as low severity Security advisory because the issuer url is provided by CDK users who define the CDK application. If they insist on connecting to a unauthorized OIDC provider, CDK should not disallow this. Additionally, the code block is run in a Lambda environment which mitigate the MITM attack. The patch is in progress. To mitigate, upgrade to CDK v2.177.0 (Expected release date 2025-02-22). Once upgraded, users should make sure the feature flag '@aws-cdk/aws-iam:oidcRejectUnauthorizedConnections' is set to true in `cdk.context.json` or `cdk.json`. There are no known workarounds for this vulnerability.

References

Community reviews

Loading reviews…