CVE-2026-34073: pyca cryptography · Improper Certificate Validation
Affects pyca cryptographySource CVE Database V5
Not known to be exploited · CVSS 1.7 Low : upgrade to 46.0.6 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 46.0.6
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 31 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade pyca cryptography to 46.0.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pycacryptography | Affected
| Fixed in
|
PyPIcryptographypkg:pypi/cryptographyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The definitive mitigation is to upgrade all instances of the pyca cryptography package to version 46.0.6 or later, where the certificate validation logic has been corrected to properly enforce DNS name constraints against the peer name during validation. Organizations should audit their Python environments and dependency management systems to identify and update vulnerable versions. Additionally, developers should review their certificate validation configurations to ensure no custom validation logic bypasses standard checks. Employing certificate pinning or additional validation layers can provide defense-in-depth. Monitoring network traffic for unusual TLS certificate chains or unexpected domain names can help detect potential exploitation attempts. Finally, educating developers and security teams about the importance of timely dependency updates and secure certificate validation practices will reduce exposure to similar vulnerabilities.
Description
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to version 46.0.6, 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 issue has been patched in version 46.0.6.