CVE-2025-23206

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.3% (26th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-0113 (ENISA EUVD) · GHSA-v4mq-x674-ff73 (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 17, 2025

Last Modified

January 23, 2026

Advisory Details (6)

Auto-updated Sep 19, 2026
Patch available. Sources: github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

IAM OIDC custom resource allows connection to unauthorized OIDC provider · Advisory · aws/aws-cdk · GitHub

https://github.com/aws/aws-cdk/security/advisories/GHSA-v4mq-x674-ff73
GitHub release Patch Available

v2.177.0

Patch available: aws/aws-cdk v2.177.0

https://github.com/aws/aws-cdk/releases/tag/v2.177.0
GitHub pull request

fix(custom-resource-handlers): do not allow unauthorized connection for iam OIDC connection (under feature flag)

Fix merged in aws/aws-cdk PR #32921 on 2025-01-16 — awaiting tagged release

https://github.com/aws/aws-cdk/pull/32921
Web page

custom-resource-handlers: IAM OIDC Provider reject unauthorized connection · Issue #32920 · aws/aws-cdk · GitHub

https://github.com/aws/aws-cdk/issues/32920
Web page

aws-cdk/packages/@aws-cdk/custom-resource-handlers/lib/aws-iam/oidc-handler/external.ts at d16482fc8a4a3e1f62751f481b770c09034df7d2 · aws/aws-cdk · GitHub

https://github.com/aws/aws-cdk/blob/d16482fc8a4a3e1f62751f481b770c09034df7d2/packages/%40aws-cdk/custom-resource-handlers/lib/aws-iam/oidc-handler/external.ts#L34
Web page

AWS CDK feature flags - AWS Cloud Development Kit (AWS CDK) v2

https://docs.aws.amazon.com/cdk/v2/guide/featureflags.html

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmaws-cdk-lib @ 2.177.0 (fixes < 2.177.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
aws-cdk-lib—
  • every version up to 2.177.0: fixed in 2.177.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 195 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  3. 2026-11-01 08:09 UTCGHSA enrichmentGHSA-v4mq-x674-ff73 · GitHub severity LOW
  4. 2026-11-01 08:09 UTCEG score recompute
  5. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  6. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  7. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  9. 2026-10-27 17:57 UTCEG score recompute
  10. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  12. 2026-10-25 16:41 UTCEG score recompute
  13. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-10-18 23:22 UTCEG score recompute
  21. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-10-18 05:44 UTCEG score recompute
  23. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
Show 71 more
  1. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-10-12 17:18 UTCEG score recompute
  4. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-11 20:50 UTCEG score recompute
  6. 2026-10-11 19:00 UTCEG score recompute
  7. 2026-10-11 15:39 UTCEG score recompute
  8. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-10-03 01:40 UTCOSV refresh
  18. 2026-10-02 16:26 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  19. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  23. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  24. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  26. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  27. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  28. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  29. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  30. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  31. 2026-09-15 03:09 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  32. 2026-09-13 23:19 UTCOSV refresh
  33. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  34. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  35. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  36. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  37. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  38. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  39. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  40. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  41. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  42. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  43. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  44. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  45. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  46. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  47. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  48. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  49. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  50. 2026-08-26 00:39 UTCOSV refresh
  51. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  52. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  53. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  54. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  55. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  56. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  57. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  58. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  59. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  60. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  61. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  62. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  63. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  64. 2026-08-09 17:10 UTCOSV refresh
  65. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  66. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  67. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  68. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  69. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  70. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  71. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-23206?
CVE-2025-23206 is a high-severity vulnerability; its CVE record was published on January 17, 2025. 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.…
When was the CVE record for CVE-2025-23206 published?
The CVE record for CVE-2025-23206 was published on January 17, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 23, 2026; the record at its source may have been updated since.
Is CVE-2025-23206 actively exploited?
CVE-2025-23206 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-23206?
CVE-2025-23206 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-23206?
A fix for CVE-2025-23206 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-23206

Explore →

Is Your Infrastructure Affected by CVE-2025-23206?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs