CVE-2026-69248

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% 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
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: Elevated riskExposed: 0

A fix is available — apply it.

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 45.0.0 through 48.0.0, if an intermediate constrained CA permits the DNS name foo.example.com, and the leaf certificate has a wildcard in its DNS SAN of *.example.com, python-cryptography's verifier accepts which allows escaping outside of the permitted names. The core issue is in DNSConstraint::matches, where a wildcard pattern was treated as matching a more-specific permitted constraint even though *.example.com can expand to sibling names such as bar.example.com outside foo.example.com. This allows acceptance of an invalid certificate chain. This issue is fixed in 49.0.0.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
47(Track)
EG Risk 47/100SSVC: Track

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
Severity69% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
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_pr, github_commit, github.
github_commit

commit 4d035a422596 (pyca/cryptography)

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

https://github.com/pyca/cryptography/commit/4d035a4225965edeffd312079a510ef25fcfdcb2
github_pr

x509: distinguish NC kinds when evaluating wildcard DNS SANs

Fix merged in pyca/cryptography PR #14888 on 2026-05-22 — awaiting tagged release

https://github.com/pyca/cryptography/pull/14888
github Patch Available🟡 PoC Available

python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees · Advisory · pyca/cryptography · GitHub

https://github.com/pyca/cryptography/security/advisories/GHSA-m2h6-j472-rp4c

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-cryptography (2.1.4-1ubuntu1.4+esm6) @ bionic2026-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 15× in last 7d / 54× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 18:25 UTCEG score recompute
  3. 2026-09-18 18:25 UTCVendor advisory
  4. 2026-09-17 16:18 UTCEG score recompute
  5. 2026-09-17 16:18 UTCVendor advisory
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 11:17 UTCEG score recompute
  8. 2026-09-16 11:17 UTCVendor advisory
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 07:00 UTCEG score recompute
  11. 2026-09-15 07:00 UTCVendor advisory
  12. 2026-09-14 04:40 UTCEG score recompute
  13. 2026-09-14 04:40 UTCVendor advisory
  14. 2026-09-13 02:33 UTCEG score recompute
  15. 2026-09-13 02:33 UTCVendor advisory
  16. 2026-09-12 00:25 UTCEG score recompute
  17. 2026-09-12 00:25 UTCVendor advisory
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-11 09:37 UTCEPSS rescore
  20. 2026-09-10 20:38 UTCEG score recompute
  21. 2026-09-10 20:38 UTCVendor advisory
  22. 2026-09-10 08:49 UTCVendor advisory
  23. 2026-09-09 06:42 UTCEG score recompute
  24. 2026-09-09 06:42 UTCVendor advisory
  25. 2026-09-08 22:01 UTCEPSS rescore
Show 64 more
  1. 2026-09-07 18:46 UTCEG score recompute
  2. 2026-09-07 16:01 UTCEPSS rescore
  3. 2026-09-06 13:47 UTCEPSS rescore
  4. 2026-09-06 06:28 UTCEG score recompute
  5. 2026-09-05 15:31 UTCEPSS rescore
  6. 2026-09-05 04:17 UTCEG score recompute
  7. 2026-09-04 05:07 UTCEPSS rescore
  8. 2026-09-02 14:34 UTCEG score recompute
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-02 13:41 UTCEG score recompute
  11. 2026-09-02 07:47 UTCEG score recompute
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-09-01 04:40 UTCEPSS rescore
  14. 2026-08-31 00:03 UTCEG score recompute
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-29 21:56 UTCEG score recompute
  18. 2026-08-28 21:42 UTCEPSS rescore
  19. 2026-08-27 15:00 UTCEG score recompute
  20. 2026-08-26 14:47 UTCEPSS rescore
  21. 2026-08-26 12:53 UTCEG score recompute
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 10:46 UTCEG score recompute
  24. 2026-08-23 06:13 UTCEG score recompute
  25. 2026-08-23 00:19 UTCEPSS rescore
  26. 2026-08-22 04:06 UTCEG score recompute
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-21 01:59 UTCEG score recompute
  29. 2026-08-20 22:56 UTCEPSS rescore
  30. 2026-08-19 23:52 UTCEG score recompute
  31. 2026-08-19 17:04 UTCEPSS rescore
  32. 2026-08-18 21:44 UTCEG score recompute
  33. 2026-08-18 13:49 UTCEPSS rescore
  34. 2026-08-18 13:49 UTCEPSS rescore
  35. 2026-08-17 19:35 UTCEG score recompute
  36. 2026-08-17 13:47 UTCEPSS rescore
  37. 2026-08-16 15:48 UTCEG score recompute
  38. 2026-08-16 14:56 UTCEPSS rescore
  39. 2026-08-16 14:56 UTCEPSS rescore
  40. 2026-08-16 02:15 UTCEPSS rescore
  41. 2026-08-15 13:42 UTCEG score recompute
  42. 2026-08-15 01:30 UTCEPSS rescore
  43. 2026-08-14 11:35 UTCEG score recompute
  44. 2026-08-13 22:00 UTCEPSS rescore
  45. 2026-08-13 09:28 UTCEG score recompute
  46. 2026-08-12 13:51 UTCEPSS rescore
  47. 2026-08-12 07:22 UTCEG score recompute
  48. 2026-08-11 05:14 UTCEG score recompute
  49. 2026-08-11 00:00 UTCEPSS rescore
  50. 2026-08-10 03:07 UTCEG score recompute
  51. 2026-08-09 13:47 UTCEPSS rescore
  52. 2026-08-09 01:01 UTCEG score recompute
  53. 2026-08-08 16:37 UTCEPSS rescore
  54. 2026-08-07 22:54 UTCEG score recompute
  55. 2026-08-06 20:47 UTCEG score recompute
  56. 2026-08-06 13:47 UTCEPSS rescore
  57. 2026-08-05 19:17 UTCEPSS rescore
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-04 16:34 UTCEG score recompute
  60. 2026-08-04 15:38 UTCEG score recompute
  61. 2026-08-04 15:10 UTCEPSS rescore
  62. 2026-08-03 22:21 UTCEG score recompute
  63. 2026-08-03 21:38 UTCEG score recompute
  64. 2026-08-03 21:38 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69248?
CVE-2026-69248 is a medium vulnerability published on August 3, 2026. cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 45.0.0 through 48.0.0, if an intermediate constrained CA permits the DNS name foo.example.com, and the leaf certificate has a wildcard in its DNS SAN of .example.com,…
When was CVE-2026-69248 disclosed?
CVE-2026-69248 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-69248 actively exploited?
CVE-2026-69248 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 91.6% of all scored CVEs.
What is the CVSS score of CVE-2026-69248?
CVE-2026-69248 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-69248?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69248, 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-69248

Explore →

Is Your Infrastructure Affected by CVE-2026-69248?

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