Advisory

GHSA-m959-cc7f-wv43

Also known as: CVE-2026-34073, PYSEC-2026-35

Summary

cryptography has incomplete DNS name constraint enforcement on peer names

Details

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

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-03-27 19:56 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

cryptography

PyPI · All systems

Affected

  • introduced 0, fixed 46.0.6 (ecosystem)

Fixed versions

46.0.6

Fix

  • Fixed version 46.0.6
    pip install --upgrade cryptography==46.0.6

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences