# python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees Advisory record · `GHSA-m2h6-j472-rp4c` - **Identifiers:** `GHSA-m2h6-j472-rp4c` · `CVE-2026-69248` · `PYSEC-2026-3554` - **State:** Confirmed - **Severity:** CVSS 6.9 Medium - **Critical:** No - **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html) - **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) - **Published:** 3 Aug 2026 - **Updated:** 24 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 3 Aug 2026, 21:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `cryptography` (PyPI): affected `>=45.0.0, <49.0.0`; fixed in `49.0.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The cryptography package (PyPI) versions 45.0.0 up to but not including 49.0.0 is affected. A flaw in its certificate verifier lets a wildcard DNS name in a leaf certificate, such as \*.example.com, pass checks against an intermediate CA's permitted name constraint for foo.example.com, so names outside the permitted set can be accepted. An attacker who can present such a certificate chain could get it accepted as valid. Upgrade to cryptography 49.0.0 or later. No workaround is given. 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 - 6.9 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0024, the 15th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Jul 2026, 13:43 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/pyca/cryptography/security/advisories/GHSA-m2h6-j472-rp4c) - 31 Oct 2026, 14:09 UTC: First seen by agentprime - 31 Oct 2026, 14:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m2h6-j472-rp4c) ## Sources - [GitHub Advisory Database: GHSA-m2h6-j472-rp4c](https://github.com/advisories/GHSA-m2h6-j472-rp4c) - [OSV: GHSA-m2h6-j472-rp4c](https://osv.dev/vulnerability/GHSA-m2h6-j472-rp4c) - - - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .