CVE-2026-69248

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (15th 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
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-52448 (ENISA EUVD) · GHSA-m2h6-j472-rp4c (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.2%CVSS: 6.9Exploit: No code on recordExposed services: Not assessed

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.9MEDIUMmedium confidence
EG Risk
47
EG Risk 47/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)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.2%
EPSS %ILE
15th
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 (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

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

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

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 advisoryMentions a patch (unverified)

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

Vendor Advisories for CVE-2026-69248(9)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-cryptography (46.0.5-1ubuntu2.2) @ resolute2026-10-29ubuntu
redhatrhaii/vllm-cuda-rhel9:17900901312026-09-23redhat
redhatrhaii/vllm-rocm-rhel9:17901096202026-09-23redhat
redhatrhaii/vllm-cpu-rhel9:17900757932026-09-23redhat
redhatrhaii/vllm-spyre-rhel9:17900761412026-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 >= 45.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 ... 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)
  • 45.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 11× in last 7d / 49× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 165 refreshes 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 65 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-69248?
CVE-2026-69248 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-69248 published?
The CVE record for CVE-2026-69248 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-69248 actively exploited?
CVE-2026-69248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69248?
CVE-2026-69248 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69248?
A fix for CVE-2026-69248 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69248 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-69248

Explore →

Is Your Infrastructure Affected by CVE-2026-69248?

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

Book a Demo →Browse All CVEs