Is cryptography 41.0 vulnerable?
PyPI · 8 releases from 41.0.0 to 41.0.7 · latest cryptography is 50.0.2 · checked 18 Nov 2026
Yes: 7 known advisories
Yes. cryptography 41.0.7, the last 41.0 release, is affected by 7 known security advisories (4 high, 2 medium, 1 low), including CVE-2026-26007, CVE-2024-26130, CVE-2023-50782. 4 more affect earlier 41.0.x releases. Upgrade to 48.0.1 or later to fix all of them.
pip install 'cryptography>=48.0.1'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 41.0.7
Vulnerable OpenSSL included in cryptography wheels
- Affected
- >=0.5.0 <48.0.1
- Fixed in
- 48.0.1
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
pyca/cryptography has a vulnerable OpenSSL included in cryptography wheels
- Affected
- >=37.0.0 <43.0.1
- Fixed in
- 43.0.1
cryptography NULL pointer dereference with pkcs12.serialize_key_and_certificates when called with a non-matching certificate and private key and an hmac_hash override
- Affected
- >=38.0.0 <42.0.4
- Fixed in
- 42.0.4
Python Cryptography package vulnerable to Bleichenbacher timing oracle attack
- Affected
- <42.0.0
- Fixed in
- 42.0.0
Null pointer dereference in PKCS12 parsing
- Affected
- <42.0.2
- Fixed in
- 42.0.2
Fixed within 41.0.x, affecting earlier releases
cryptography vulnerable to NULL-dereference when loading PKCS7 certificates
- Affected
- >=3.1 <41.0.6
- Fixed in
- 41.0.6
Vulnerable OpenSSL included in cryptography wheels
- Affected
- >=2.5 <41.0.4
- Fixed in
- 41.0.4
pyca/cryptography's wheels include vulnerable OpenSSL
- Affected
- >=0.8 <41.0.3
- Fixed in
- 41.0.3
cryptography mishandles SSH certificates
- Affected
- >=40.0.0 <41.0.2
- Fixed in
- 41.0.2
Every cryptography 41.0.x release
Affected: 41.0.0 to 41.0.7. Latest cryptography: 50.0.2.
| Version | Known advisories |
|---|---|
| cryptography 41.0.7 | GHSA-537c-gmf6-5ccf, CVE-2026-34073, CVE-2026-26007, GHSA-h4gh-qq45-vh27, CVE-2024-26130, CVE-2023-50782, CVE-2024-0727 |
| cryptography 41.0.6 | GHSA-537c-gmf6-5ccf, CVE-2026-34073, CVE-2026-26007, GHSA-h4gh-qq45-vh27, CVE-2024-26130, CVE-2023-50782, CVE-2024-0727 |
| cryptography 41.0.5 | GHSA-537c-gmf6-5ccf, CVE-2026-34073, CVE-2026-26007, GHSA-h4gh-qq45-vh27, CVE-2024-26130, CVE-2023-50782, CVE-2024-0727, CVE-2023-49083 |
| cryptography 41.0.4 | GHSA-537c-gmf6-5ccf, CVE-2026-34073, CVE-2026-26007, GHSA-h4gh-qq45-vh27, CVE-2024-26130, CVE-2023-50782, CVE-2024-0727, CVE-2023-49083 |
| cryptography 41.0.3 | GHSA-537c-gmf6-5ccf, CVE-2026-34073, CVE-2026-26007, GHSA-h4gh-qq45-vh27, CVE-2024-26130, CVE-2023-50782, CVE-2024-0727, CVE-2023-49083, GHSA-v8gr-m533-ghj9 |
| cryptography 41.0.2 | GHSA-537c-gmf6-5ccf, CVE-2026-34073, CVE-2026-26007, GHSA-h4gh-qq45-vh27, CVE-2024-26130, CVE-2023-50782, CVE-2024-0727, CVE-2023-49083, GHSA-v8gr-m533-ghj9, GHSA-jm77-qphf-c4w8 |
| cryptography 41.0.1 | GHSA-537c-gmf6-5ccf, CVE-2026-34073, CVE-2026-26007, GHSA-h4gh-qq45-vh27, CVE-2024-26130, CVE-2023-50782, CVE-2024-0727, CVE-2023-49083, GHSA-v8gr-m533-ghj9, GHSA-jm77-qphf-c4w8, CVE-2023-38325 |
| cryptography 41.0.0 | GHSA-537c-gmf6-5ccf, CVE-2026-34073, CVE-2026-26007, GHSA-h4gh-qq45-vh27, CVE-2024-26130, CVE-2023-50782, CVE-2024-0727, CVE-2023-49083, GHSA-v8gr-m533-ghj9, GHSA-jm77-qphf-c4w8, CVE-2023-38325 |
Which of your client projects are still on cryptography 41.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.