Advisory record · GHSA-m959-cc7f-wv43

cryptography has incomplete DNS name constraint enforcement on peer names

CVSS 1.7 LowEPSS 0.0023 · 13th percentile

Published by the GitHub Advisory Database at 27 Mar 2026, 19:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
cryptographyPyPI<46.0.646.0.6
Identifiers
GHSA-m959-cc7f-wv43 · CVE-2026-34073 · PYSEC-2026-35
Weakness (CWE)
CWE-295
Published
27 Mar 2026
Updated
10 Sept 2026

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.

Written 1 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 25 Mar 2026, 23:27 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:11 UTC First seen by agentprime
  3. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.