Sign in
Deutsch English Español Polski
Low

cryptography has incomplete DNS name constraint enforcement on peer names

  • Disclosed: 27.03.2026
  • Updated: 11.10.2026 15:17

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

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) cryptography < 46.0.6 46.0.6

References

CVSS score 5.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Weakness (CWE)
CWE-295
Platform
Python (PyPI)
Package
cryptography
Disclosed
27.03.2026
Updated
11.10.2026 15:17

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2026-35 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-m959-cc7f-wv43 - CC BY 4.0

Vulnerability history: cryptography

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (24) in the archive
Total entries
24
First → latest
03.2017 08.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 12
  • Medium 7
  • Low 5

Disclosures per year

Severity:
  1. python-cryptography: Duplicate self-signed intermediates can cause exponential path-building
    High CVE-2026-69249 >= 42.0.0, < 49.0.0 49.0.0
  2. cryptography: PKCS#7 EnvelopedData decryption exposes a Bleichenbacher oracle through distinguishable errors and timing
    High CVE-2026-69247 >= 44.0.0, < 50.0.0 50.0.0
  3. Vulnerable OpenSSL included in cryptography wheels
    High · 7.5 ghsa-537c-gmf6-5ccf >= 0.5.0, < 48.0.1 48.0.1
  4. cryptography has incomplete DNS name constraint enforcement on peer names this entry
    Low · 5.3 CVE-2026-34073 < 46.0.6 46.0.6
  5. cryptography Vulnerable to a Subgroup Attack Due to Missing Subgroup Validation for SECT Curves
    High CVE-2026-26007 < 46.0.5 46.0.5
  6. cryptography NULL pointer dereference with pkcs12.serialize_key_and_certificates when called with a non-matching certificate and private key and an hmac_hash override
    High · 7.5 CVE-2024-26130 >= 38.0.0, < 42.0.4 42.0.4
  7. Python Cryptography package vulnerable to Bleichenbacher timing oracle attack
    High · 7.5 CVE-2023-50782 < 42.0.0 42.0.0
  8. cryptography mishandles SSH certificates
    High · 7.5 CVE-2023-38325 >= 40.0.0, < 41.0.2 41.0.2
  9. Vulnerable OpenSSL included in cryptography wheels
    High · 7.4 CVE-2023-0286 >= 0.8.1, < 39.0.1 39.0.1
  10. PyCA Cryptography symmetrically encrypting large values can lead to integer overflow
    High · 9.1 CVE-2020-36242 >= 3.1, < 3.3.2 3.3.2
  11. RSA decryption vulnerable to Bleichenbacher timing vulnerability
    High · 5.9 CVE-2020-25659 < 3.2 3.2
  12. PyCA Cryptography vulnerable to GCM tag forgery
    High · 7.5 CVE-2018-10903 >= 1.9.0, < 2.3 2.3
  13. Improper input validation in cryptography
    High · 7.5 CVE-2016-9243 < 1.5.3 1.5.3

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Privacy policy

Free to subscribe. Unsubscribe with one click in any email.