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%, top 83% of all CVEs by exploit prediction. 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%CVSS: 8.7Exploit: Elevated riskExposed: 0

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.7(medium)
EG Risk
70(Attend)
EG Risk 70/100SSVC: Attend

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%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

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(5)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-cryptography (46.0.5-1ubuntu2.2) @ resolute2026-09-18ubuntu
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 rangeFixed inDependents
python-cryptography3.3.2-1 ... 49.0.0-2 (34 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-cryptography38.0.4-3 ... 49.0.0-2 (28 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-cryptography43.0.0-3 ... 49.0.0-2 (17 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-cryptography43.0.0-3 ... 49.0.0-1~exp1 (14 versions)49.0.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
cryptography0.1 ... 48.0.1 (156 versions)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 20× in last 7d / 87× 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 124 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 83.0% of all scored CVEs.
What is the CVSS score of CVE-2026-69249?
CVE-2026-69249 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-69249?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69249, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs