# CVE-2026-69248 — pyca cryptography

> As of 2026-08-03, CVE-2026-69248 is a Medium-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in pyca cryptography, CVSS v4.0 6.9. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-69248 as of 2026-08-03; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-08-03

## What is CVE-2026-69248?

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

The record classifies CVE-2026-69248 under weakness class [CWE-295](https://intel.threadlinqs.com/cwe/CWE-295). 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 63 days ago.

## Severity and exploitation probability

- **CVSS v4.0 base score:** 6.9 — Medium (derived from score) (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-08-03

## Is CVE-2026-69248 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **pyca**: cryptography

## How to fix CVE-2026-69248

No vendor patch reference has been recorded for CVE-2026-69248 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-69248

No threat campaign in the Threadlinqs corpus currently references CVE-2026-69248, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org. Last verified by Threadlinqs on 2026-08-04.

**Vendor advisory and patch**

- [github.com](https://github.com/pyca/cryptography/security/advisories/GHSA-m2h6-j472-rp4c)

**Other references**

- [github.com](https://github.com/pyca/cryptography/pull/14888)
- [github.com (4d035a4225965edeffd312079a510ef25fcfdcb2)](https://github.com/pyca/cryptography/commit/4d035a4225965edeffd312079a510ef25fcfdcb2)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-69248
Full detection coverage and IOCs for threats exploiting CVE-2026-69248 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp