CVE-2026-34073: cryptography has incomplete DNS name constraint enforcement on peer names
Summary In versions of cryptography prior to 46.0.5, DNS name constraints were only validated against SANs within child certificates, and not the "peer name" presented during each validation. Consequently, cryptography would allow a peer named bar.example.com to validate against a wildcard leaf certificate for .example.com, even if the leaf's parent certificate (or upwards) contained an excluded subtree constraint…
Published Mar 27, 2026 · Updated Jun 5, 2026
Affected packages
cryptography
- Ecosystem
- PyPI
- Affected
- < 46.0.6
- Fixed in
- 46.0.6
- Check
pip show cryptography
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
In versions of cryptography prior to 46.0.5, DNS name constraints were only validated against SANs within child certificates, and not the "peer name" presented during each validation. Consequently, cryptography would allow a peer named bar.example.com to validate against a wildcard leaf certificate for *.example.com, even if the leaf's parent certificate (or upwards) contained an excluded subtree constraint for bar.example.com.
This behavior resulted from a gap between RFC 5280 (which defines Name Constraint semantics) and RFC 9525 (which defines service identity semantics): put together, neither states definitively whether Name Constraints should be applied to peer names. To close this gap, cryptography now conservatively rejects any validation where the peer name would be rejected by a name constraint if it were a SAN instead.
In practice, exploitation of this bypass requires an uncommon X.509 topology, one that the Web PKI avoids because it exhibits these kinds of problems. Consequently, we consider this a medium-to-low impact severity.
See CVE-2025-61727 for a similar bypass in Go's crypto/x509.
Remediation
Users should upgrade to 46.0.6 or newer.
Attribution
Reporter: @1seal
Credited to 1seal, woodruffw.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-69247
cryptography: PKCS#7 EnvelopedData decryption exposes a Bleichenbacher oracle through distinguishable errors and timing
high8.2Aug 3, 2026CVE-2026-69248
python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees
medium6.9Aug 3, 2026CVE-2026-69249
python-cryptography: Duplicate self-signed intermediates can cause exponential path-building
high8.7Aug 3, 2026GHSA-537c-gmf6-5ccf
Vulnerable OpenSSL included in cryptography wheels
high7.5Jun 15, 2026CVE-2026-39892
Cryptography vulnerable to buffer overflow if non-contiguous buffers were passed to APIs
medium9.8Apr 8, 2026CVE-2026-26007
cryptography Vulnerable to a Subgroup Attack Due to Missing Subgroup Validation for SECT Curves
high8.2Feb 10, 2026
