CVE-2026-69249

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (15th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.7Exploit: Elevated riskExposed 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 v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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
15th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 3, 2026

Last Modified

September 10, 2026

Advisory Details (3)

Auto-updated Aug 3, 2026
🔬 Proof of concept available. 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_pr

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 Patch Available🟡 PoC Available

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

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

Vendor Advisories for CVE-2026-69249(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-cryptography (46.0.5-1ubuntu2.2) @ resolute2026-10-04ubuntu
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

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 ... 49.0.0-2 (28 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography43.0.0-3 ... 49.0.0-2 (17 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

(3)

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 19× in last 7d / 84× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 166 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-69249?
CVE-2026-69249 is a high vulnerability 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 CVE-2026-69249 disclosed?
CVE-2026-69249 was first published on August 3, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (15th 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.

Book a Demo →Browse All CVEs