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.2%, top 91% 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
Elevated
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 49.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
9%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 4, 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(2)

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

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-2 (16 versions)——
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.

Data Freshness Timeline

(refreshed 16× in last 7d / 39× 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.

  1. 2026-08-21 03:29 UTCEG score recompute
  2. 2026-08-20 22:56 UTCEPSS rescore
  3. 2026-08-20 00:11 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 21:51 UTCEG score recompute
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-17 19:35 UTCEG score recompute
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 16:40 UTCEG score recompute
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 03:29 UTCEG score recompute
  14. 2026-08-16 02:15 UTCEPSS rescore
  15. 2026-08-15 14:21 UTCEG score recompute
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-13 22:56 UTCEG score recompute
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 20:40 UTCEG score recompute
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-11 18:24 UTCEG score recompute
  22. 2026-08-11 05:15 UTCEG score recompute
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 13:50 UTCEG score recompute
  25. 2026-08-09 13:47 UTCEPSS rescore
Show 14 more
  1. 2026-08-09 00:42 UTCEG score recompute
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-07 22:25 UTCEG score recompute
  4. 2026-08-06 20:09 UTCEG score recompute
  5. 2026-08-06 13:47 UTCEPSS rescore
  6. 2026-08-06 07:01 UTCEG score recompute
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-05 19:17 UTCEPSS rescore
  9. 2026-08-04 15:20 UTCEG score recompute
  10. 2026-08-04 15:10 UTCEPSS rescore
  11. 2026-08-04 14:49 UTCEG score recompute
  12. 2026-08-03 22:21 UTCEG score recompute
  13. 2026-08-03 21:38 UTCEG score recompute
  14. 2026-08-03 21:38 UTCMITRE cvelistV5first tracked

Related CVEs(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. Prior to 49.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…
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 August 4, 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 90.8% 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