Is cryptography 46.0 vulnerable?
PyPI · 8 releases from 46.0.0 to 46.0.7 · latest cryptography is 50.0.2 · checked 18 Nov 2026
Yes: 4 known advisories
Yes. cryptography 46.0.7, the last 46.0 release, is affected by 4 known security advisories (3 high, 1 medium), including CVE-2026-69249, CVE-2026-69247, CVE-2026-69248. 3 more affect earlier 46.0.x releases. Upgrade to 50.0.0 or later to fix all of them.
pip install 'cryptography>=50.0.0'Is your project on an affected cryptography?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting cryptography 46.0.7
python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees
- Affected
- >=45.0.0 <49.0.0
- Fixed in
- 49.0.0
python-cryptography: Duplicate self-signed intermediates can cause exponential path-building
- Affected
- >=42.0.0 <49.0.0
- Fixed in
- 49.0.0
cryptography: PKCS#7 EnvelopedData decryption exposes a Bleichenbacher oracle through distinguishable errors and timing
- Affected
- >=44.0.0 <50.0.0
- Fixed in
- 50.0.0
Vulnerable OpenSSL included in cryptography wheels
- Affected
- >=0.5.0 <48.0.1
- Fixed in
- 48.0.1
Fixed within 46.0.x, affecting earlier releases
Cryptography vulnerable to buffer overflow if non-contiguous buffers were passed to APIs
- Affected
- >=45.0.0 <46.0.7
- Fixed in
- 46.0.7
cryptography has incomplete DNS name constraint enforcement on peer names
- Affected
- <46.0.6
- Fixed in
- 46.0.6
cryptography Vulnerable to a Subgroup Attack Due to Missing Subgroup Validation for SECT Curves
- Affected
- <46.0.5
- Fixed in
- 46.0.5
Every cryptography 46.0.x release
Affected: 46.0.0 to 46.0.7. Latest cryptography: 50.0.2.
| Version | Known advisories |
|---|---|
| cryptography 46.0.7 | CVE-2026-69248, CVE-2026-69249, CVE-2026-69247, GHSA-537c-gmf6-5ccf |
| cryptography 46.0.6 | CVE-2026-69248, CVE-2026-69249, CVE-2026-69247, GHSA-537c-gmf6-5ccf, CVE-2026-39892 |
| cryptography 46.0.5 | CVE-2026-69248, CVE-2026-69249, CVE-2026-69247, GHSA-537c-gmf6-5ccf, CVE-2026-39892, CVE-2026-34073 |
| cryptography 46.0.4 | CVE-2026-69248, CVE-2026-69249, CVE-2026-69247, GHSA-537c-gmf6-5ccf, CVE-2026-39892, CVE-2026-34073, CVE-2026-26007 |
| cryptography 46.0.3 | CVE-2026-69248, CVE-2026-69249, CVE-2026-69247, GHSA-537c-gmf6-5ccf, CVE-2026-39892, CVE-2026-34073, CVE-2026-26007 |
| cryptography 46.0.2 | CVE-2026-69248, CVE-2026-69249, CVE-2026-69247, GHSA-537c-gmf6-5ccf, CVE-2026-39892, CVE-2026-34073, CVE-2026-26007 |
| cryptography 46.0.1 | CVE-2026-69248, CVE-2026-69249, CVE-2026-69247, GHSA-537c-gmf6-5ccf, CVE-2026-39892, CVE-2026-34073, CVE-2026-26007 |
| cryptography 46.0.0 | CVE-2026-69248, CVE-2026-69249, CVE-2026-69247, GHSA-537c-gmf6-5ccf, CVE-2026-39892, CVE-2026-34073, CVE-2026-26007 |
Which of your client projects are still on cryptography 46.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact cryptography version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other cryptography versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.