Vulnerability Database · Alpine · Package report

py3-cryptography: vulnerability history, versions and safety

py3-cryptography is a package in the Alpine ecosystem. Vulert records 5 vulnerabilities for it across 85 releases, from Feb 2023 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 08 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on py3-cryptography i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 08 Apr 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 5 vulnerabilities on record across 3 years, 3 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 5 over 3 years · 3 in the last year i
  • Latest disclosure 08 Apr 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for py3-cryptography, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
46.0.5-r0 U2 Yes Details →
46.0.3-r0 U3 Yes Details →
46.0.2-r0 U3 Yes Details →
44.0.3-r0 U3 Yes Details →
44.0.2-r0 U3 Yes Details →
44.0.1-r0 U3 Yes Details →
44.0.0-r0 U3 Yes Details →
43.0.3-r0 U3 Yes Details →
43.0.1-r0 U3 Yes Details →
43.0.0-r0 U3 Yes Details →
42.0.8-r0 U3 Yes Details →
42.0.7-r0 U3 Yes Details →
42.0.5-r1 U3 Yes Details →
42.0.5-r0 U3 Yes Details →
41.0.7-r0 U3 Yes Details →
41.0.5-r0 U3 Yes Details →
41.0.4-r0 U3 Yes Details →
41.0.3-r0 U3 Yes Details →
41.0.2-r2 U3 Yes Details →
41.0.2-r1 U3 Yes Details →
41.0.2-r0 U3 Yes Details →
41.0.1-r0 U4 Yes Details →
41.0.0-r0 U4 Yes Details →
40.0.2-r1 U4 Yes Details →
40.0.2-r0 U4 Yes Details →
40.0.1-r0 U4 Yes Details →
40.0.0-r0 U4 Yes Details →
39.0.2-r0 U4 Yes Details →
39.0.1-r0 U4 Yes Details →
39.0.0-r0 U5 Yes Details →
38.0.4-r0 U5 Yes Details →
38.0.3-r1 U5 Yes Details →
38.0.3-r0 U5 Yes Details →
38.0.2-r0 U5 Yes Details →
38.0.1-r0 U5 Yes Details →
37.0.4-r2 U5 Yes Details →
37.0.4-r1 U5 Yes Details →
37.0.4-r0 U5 Yes Details →
3.4.8-r1 U5 Yes Details →
3.4.8-r0 U5 Yes Details →
3.3.2-r4 U5 Yes Details →
3.3.2-r3 U5 Yes Details →
3.3.2-r2 U5 Yes Details →
3.3.2-r1 U5 Yes Details →
3.3.2-r0 U5 Yes Details →
3.3.1-r0 U5 Yes Details →
3.3-r0 U5 Yes Details →
3.2.1-r0 U5 Yes Details →
2.9.2-r0 U5 Yes Details →
2.9-r0 U5 Yes Details →
2.8-r1 U5 Yes Details →
2.8-r0 U5 Yes Details →
2.7-r1 U5 Yes Details →
2.7-r0 U5 Yes Details →
2.6.1-r1 U5 Yes Details →
2.6.1-r0 U5 Yes Details →
2.5-r0 U5 Yes Details →
2.4.2-r2 U5 Yes Details →
2.4.2-r1 U5 Yes Details →
2.4.2-r0 U5 Yes Details →
2.3.1-r1 U5 Yes Details →
2.3.1-r0 U5 Yes Details →
2.2.2-r0 U5 Yes Details →
2.1.4-r1 U5 Yes Details →
2.1.4-r0 U5 Yes Details →
2.1.3-r0 U5 Yes Details →
2.0.3-r1 U5 Yes Details →
2.0.3-r0 U5 Yes Details →
2.0.2-r0 U5 Yes Details →
1.9-r0 U5 Yes Details →
1.8.1-r1 U5 Yes Details →
1.8.1-r0 U5 Yes Details →
1.7.2-r1 U5 Yes Details →
1.7.2-r0 U5 Yes Details →
1.5.3-r0 U5 Yes Details →
1.5.2-r1 U5 Yes Details →
1.5.2-r0 U5 Yes Details →
1.4-r2 U5 Yes Details →
1.4-r1 U5 Yes Details →
1.4-r0 U5 Yes Details →
1.3.2-r0 U5 Yes Details →
1.3.1-r0 U5 Yes Details →
1.0.2-r0 U5 Yes Details →
0.8.2-r0 U5 Yes Details →
0.6.1-r0 U5 Yes Details →

Newest 85 of 85 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for py3-cryptography

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About py3-cryptography

Is py3-cryptography safe to use?

Vulert records 5 vulnerabilities for py3-cryptography in Alpine: 0 critical, 0 high, 0 medium and 0 low, plus 5 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does py3-cryptography have?

5 vulnerabilities are recorded for py3-cryptography in the Alpine ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new py3-cryptography vulnerabilities disclosed?

3 vulnerabilities were recorded for py3-cryptography in the last 12 months, and the oldest entry in this database dates to 07 Feb 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of py3-cryptography are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor py3-cryptography for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the py3-cryptography version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.