VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

jwcrypto: vulnerability history, versions and safety

jwcrypto is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 32 releases, from Sep 2016 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded M5 U5
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
4 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jwcrypto vulnerabilities

Vulert verdict on jwcrypto 1.6.1 i

Updated on 22 Oct 2026

Careful: 1.6.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.6.1 — affected i
  • Vulnerabilities on record 10 over 9 years · 4 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 6.8 i
  • With no published fix 1 i
  • Depended on by 857 packages i
  • Stars 478 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence LGPL-3.0-or-later i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

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 tracks for jwcrypto, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.6.1 15 Sep 2026 M1 LGPL-3.0-or-later No Details →
1.6.0 01 Sep 2026 M1 LGPL-3.0-or-later No Details →
1.5.9 26 Aug 2026 M1 LGPL-3.0-or-later No Details →
1.5.8 24 Jun 2026 M1 LGPL-3.0-or-later No Details →
1.5.7 07 Apr 2026 M1 LGPL-3.0-or-later No Details →
1.5.6 06 Mar 2024 M1 U1 non-standard No Details →
1.5.5 05 Mar 2024 M2 U2 non-standard No Details →
1.5.4 13 Feb 2024 M2 U2 non-standard No Details →
1.5.3 07 Feb 2024 M2 U2 non-standard No Details →
1.5.2 07 Feb 2024 M2 U2 non-standard No Details →
1.5.1 26 Dec 2023 M2 U2 non-standard No Details →
1.5.0 30 May 2023 M3 U3 non-standard No Details →
1.4.2 15 Sep 2022 M3 U3 non-standard No Details →
1.4.1 14 Sep 2022 M3 U3 non-standard No Details →
1.4.0 13 Sep 2022 M3 U3 non-standard No Details →
1.3.1 21 May 2022 M4 U4 non-standard No Details →
1.3.0 12 May 2022 M4 U4 non-standard No Details →
1.2.0 28 Apr 2022 M4 U4 non-standard No Details →
1.0.0 02 Aug 2021 M4 U4 non-standard No Details →
0.9.1 09 Jun 2021 M4 U4 non-standard No Details →
0.9.0 01 Jun 2021 M4 U4 non-standard No Details →
0.8.0 20 Aug 2020 M4 U4 non-standard No Details →
0.7.0 19 Feb 2020 M4 U4 non-standard No Details →
0.6.0 05 Nov 2018 M4 U4 non-standard No Details →
0.5.0 27 Jun 2018 M4 U4 non-standard No Details →
0.4.2 01 Aug 2017 M4 U4 non-standard No Details →
0.4.1 24 Jul 2017 M4 U4 non-standard No Details →
0.4.0 29 Nov 2016 M4 U4 non-standard No Details →
0.3.1 19 Aug 2016 M5 U5 non-standard No Details →
0.3.0 02 Aug 2016 M5 U5 non-standard No Details →
0.2.1 14 Sep 2015 M5 U5 non-standard No Details →
0.2.0 16 Jun 2015 M5 U5 non-standard No Details →

All 32 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2016 1
  • 2022 2
  • 2023 1
  • 2024 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for jwcrypto

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-28102: JWCrypto Vulnerable to JWT Bomb Attack 6.8 medium 1.5.6 06 Mar 2024
CVE-2024-28102: jwcrypto Package Vulnerable to JWT Bomb Attack Leading to Denial of Service 6.8 medium 1.5.6 07 Jul 2026
CVE-2023-6681: Denial of Service in jwcrypto due to unbounded PBES2 Count value 5.3 medium 1.5.1 28 Dec 2023
CVE-2016-6298: jwcrypto lacks the Random Filling protection mechanism 5.3 medium 0.3.2 17 May 2022
CVE-2023-6681: jwcrypto Denial of Service Vulnerability and Resource Exhaustion Risk 5.3 medium 1.5.1 12 Feb 2024

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About jwcrypto

Is jwcrypto safe to use?

Vulert records 10 vulnerabilities for jwcrypto in PyPI: 0 critical, 0 high, 5 medium and 0 low, plus 5 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is jwcrypto's Vulert package health score?

Vulert scores jwcrypto 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of jwcrypto affected?

Yes. 1.6.1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of jwcrypto should I use?

1.6.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does jwcrypto have?

10 vulnerabilities are recorded for jwcrypto in the PyPI ecosystem: 0 critical, 0 high, 5 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 jwcrypto vulnerabilities disclosed?

4 vulnerabilities were recorded for jwcrypto in the last 12 months, and the oldest entry in this database dates to 01 Sep 2016. 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 jwcrypto 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 jwcrypto for upcoming vulnerabilities?

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