Answer in brief
CVE-2026-69248 records a Medium severity (CVSS 6.9) vulnerability in python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees. The current sources do not mark it as known exploited. The current feed maps pyca/cryptography (generic), cryptography (pip), cryptography (pip), cryptography (pypi). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps pyca/cryptography (generic), cryptography (pip), cryptography (pip), cryptography (pypi). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| pyca/cryptographygeneric | < 49.0.0 | Not reported |
| cryptographypip | <=48.0.0 | 49.0.0 |
| cryptographypip | >=45.0.0,<=48.0.0 | 49.0.0 |
| cryptographypypi | >=45.0.0 <49.0.0 | 49.0.0 |
Published upstream
Aug 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 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, 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.
Quoted source text, attributed separately from HOL analysis.