CVE-2026-34073: 
Python vulnerability analysis and mitigation

CVE-2026-34073 is a DNS name constraint bypass vulnerability in the Python cryptography library (GHSA-m959-cc7f-wv43), classified as improper certificate validation (CWE-295). Prior to version 46.0.6, the library failed to validate DNS name constraints against the "peer name" presented during TLS certificate validation — only checking constraints against Subject Alternative Names (SANs) in child certificates. This allowed a peer named bar.example.com to successfully validate against a wildcard leaf certificate for *.example.com, even when an ancestor certificate contained an excluded subtree constraint for bar.example.com. The vulnerability was reported by researcher 1seal, published on March 25, 2026, and patched in version 46.0.6. It carries a CVSS v3.1 score of 5.3 (Medium) and a CVSS v4.0 score of 1.7 (Low) (GitHub Advisory, Red Hat Bugzilla).

The root cause is CWE-295 (Improper Certificate Validation), arising from a gap between RFC 5280 (Name Constraint semantics) and RFC 9525 (service identity semantics): neither RFC definitively specifies whether Name Constraints should be applied to peer names during validation. As a result, the cryptography library only checked name constraints against SANs in the certificate chain, not against the peer name supplied at connection time. An attacker exploiting this flaw would need to control a certificate that is a wildcard leaf (e.g., *.example.com) issued under a CA whose certificate chain includes an excluded subtree constraint for the target peer name (e.g., bar.example.com). The fix conservatively rejects any validation where the peer name would be rejected by a name constraint if it were treated as a SAN. A similar bypass exists in Go's crypto/x509 (CVE-2025-61727) (GitHub Advisory).

Successful exploitation allows an attacker to present a certificate that should be rejected by name constraint rules in the certificate chain, causing the cryptography library to accept it as valid for a TLS connection. The primary impact is an integrity bypass — improperly constrained certificates can be used to impersonate services or bypass access controls enforced via X.509 name constraints. There is no confidentiality or availability impact. Exploitation requires an uncommon X.509 topology that the Web PKI deliberately avoids, limiting real-world impact to niche PKI deployments that rely on name constraint enforcement for security decisions (GitHub Advisory, Red Hat Bugzilla).

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation as of the time of this report. The EPSS score is approximately 0.023% (1st percentile), indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires a specific and uncommon X.509 certificate topology — one that the Web PKI avoids — making opportunistic mass exploitation unlikely (GitHub Advisory).

The primary remediation is to upgrade the Python cryptography library to version 46.0.6 or later, which conservatively rejects peer names that would be excluded by name constraints in the certificate chain. No configuration-based workaround is available; upgrading is the only fix. Downstream products incorporating the vulnerable library — including IBM Maximo Application Suite, IBM Process Mining, IBM Cloud Pak for Business Automation, IBM Business Automation Workflow, IBM Guardium Data Security Center, and OpenVPN Access Server — have released or are releasing updates that bundle cryptography 46.0.6 (GitHub Advisory, OpenVPN Release Notes, IBM Process Mining Advisory).

The vulnerability was disclosed by the pyca/cryptography maintainers via GitHub Security Advisory on March 25, 2026, with analyst credit to woodruffw. Red Hat opened a Bugzilla tracking entry (Bug 2453276) and rated it low severity. OpenVPN explicitly called out the fix in its Access Server 3.2.0 release notes. Multiple IBM product teams issued security bulletins acknowledging the dependency on the vulnerable library. Community discussion noted a parallel issue in Go's crypto/x509 (CVE-2025-61727), highlighting the ambiguity in RFC 5280 and RFC 9525 as a broader ecosystem concern (GitHub Advisory, OpenVPN Release Notes, Red Hat Bugzilla).