Vulnerability Database · Debian · Package report

python-jwcrypto: vulnerability history, versions and safety

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

i
8 vulnerabilities recorded U8
i
3 with no fix published

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

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

Most recent disclosure 28 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on python-jwcrypto i

Updated on 22 Oct 2026

Careful: 3 of the 8 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 8 vulnerabilities on record across 9 years, 2 in the last year.

What to do: Plan around the 3 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 8 over 9 years · 2 in the last year i
  • Latest disclosure 28 Aug 2026 i
  • Highest CVSS 5.9 i
  • With no published fix 3 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 python-jwcrypto, 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

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2016 2
  • 2024 4
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for python-jwcrypto

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 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: 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 →

Questions

About python-jwcrypto

Is python-jwcrypto safe to use?

Vulert records 8 vulnerabilities for python-jwcrypto in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 8 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does python-jwcrypto have?

8 vulnerabilities are recorded for python-jwcrypto in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 8 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 python-jwcrypto vulnerabilities disclosed?

2 vulnerabilities were recorded for python-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 python-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 python-jwcrypto for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the python-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.