Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
cryptography versions before 46.0.6 do not apply DNS name constraints to the peer name presented during certificate validation, so a peer such as bar.example.com can validate against a wildcard leaf certificate for *.example.com even when a parent certificate excludes that name. An attacker would need an uncommon X.509 certificate chain topology to exploit this, and the source describes the impact as medium-to-low. Upgrade to cryptography 46.0.6 or newer.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 1.7 | Low | 4.0 | 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:U | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0023, the 13th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 25 Mar 2026, 23:27 UTC Published by the maintainers as a GitHub repository advisory
- 31 Oct 2026, 14:11 UTC First seen by agentprime
- 31 Oct 2026, 14:11 UTC Confirmed by OSV