CVE-2026-69249

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (18th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-52450 (ENISA EUVD) · GHSA-jwv3-5hgf-82ww (GitHub Security Advisories) · PYSEC-2026-3553 (OSV.dev)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 42.0.0 through 48.0.0, when resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack. The core issue arises in the recursive nature of build_chain_inner, which does not de-duplicate against previously analyzed candidates. As the correctness of validation is not affected, the integrity of a system cannot be compromised through this vector, only its availability. This issue is fixed in 49.0.0.

CVSS
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
18th
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.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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 low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 3, 2026

Last Modified

October 23, 2026

Advisory Details (3)

Auto-updated Aug 3, 2026
Patch available. Sources: github, github_pr, github_commit.
GitHub commit

commit 4a12cf49675a (pyca/cryptography)

Fix landed in pyca/cryptography commit 4a12cf49675a — awaiting tagged release

https://github.com/pyca/cryptography/commit/4a12cf49675a184e47f912b00b04f3a629283582
GitHub pull request

Add a signature validation budget during path construction

Fix merged in pyca/cryptography PR #14960 on 2026-06-07 — awaiting tagged release

https://github.com/pyca/cryptography/pull/14960
GitHub advisoryMentions a patch (unverified)

Duplicate self-signed intermediates can cause exponential path-building · Advisory · pyca/cryptography · GitHub

https://github.com/pyca/cryptography/security/advisories/GHSA-jwv3-5hgf-82ww

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-cryptography (46.0.5-1ubuntu2.2) @ resolute2026-11-11ubuntu
redhatpython-cryptography-0:43.0.0-4.el10_2.52026-09-24redhat
redhatpython-cryptography-0:43.0.0-4.el10_0.12026-09-24redhat
redhatrhaii/vllm-spyre-rhel9:17900761412026-09-23redhat
redhatrhaii/vllm-cuda-rhel9:17900901312026-09-23redhat
redhatrhaii/vllm-rocm-rhel9:17901096202026-09-23redhat
redhatrhaii/vllm-cpu-rhel9:17900757932026-09-23redhat
redhatpython3.14-cryptography-0:45.0.4-4.el10_2.52026-09-08redhat
redhatpython3.14-cryptography-0:45.0.4-4.el9_8.62026-09-08redhat
redhatpython-cryptography-main-50.0.0-1.hum12026-08-17redhat
pipcryptography @ 49.0.0 (fixes >= 42.0.0, < 49.0.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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography3.3.2-1 ... 49.0.0-2 (34 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography38.0.4-3 ... 50.0.2-1~exp1 (29 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography43.0.0-3 ... 50.0.2-1~exp1 (18 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography43.0.0-3 ... 49.0.0-1~exp1 (14 versions)
  • every version up to 49.0.0-1: fixed in 49.0.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
cryptography0.1 ... 48.0.1 (156 versions)
  • 42.0.0 up to 49.0.0: fixed in 49.0.0
  • every version up to 49.0.0: fixed in 49.0.0
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 231 rows 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. None are among the latest 100 rows. The 131 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-69249?
CVE-2026-69249 is a high-severity vulnerability; its CVE record was published on August 3, 2026. python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 42.0.0 through 48.0.0, when resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same…
When was the CVE record for CVE-2026-69249 published?
The CVE record for CVE-2026-69249 was published on August 3, 2026. 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 October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-69249 actively exploited?
CVE-2026-69249 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69249?
CVE-2026-69249 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69249?
A fix for CVE-2026-69249 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69249 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69249

Explore →

Is Your Infrastructure Affected by CVE-2026-69249?

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