VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

python-jose: vulnerability history, versions and safety

python-jose is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 38 releases, from Jan 2017 to Oct 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 C3 M2 U5
i
3 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 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all python-jose vulnerabilities

Vulert verdict on python-jose 3.5.0 i

Updated on 23 Oct 2026

Careful: 3.5.0 has 3 known vulnerabilities, and 3 have 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 Maintaining
  • Popularity Widely used
  • Community Quiet

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 3.5.0 — affected i
  • Vulnerabilities on record 10 over 9 years · 4 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 3 i
  • Depended on by 1,937 packages i
  • Stars 1,759 i
  • OpenSSF scorecard 3/10 i
  • Last release 16 months ago i
  • Licence MIT 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 python-jose, 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
3.5.0 28 May 2025 C1 U2 MIT No Details →
3.4.0 18 Feb 2025 C1 U2 MIT No Details →
3.3.0 05 Jun 2021 C2 M2 U4 MIT No Details →
3.2.0 30 Jul 2020 C2 M2 U4 MIT No Details →
3.1.0 17 Dec 2019 C2 M2 U4 MIT No Details →
3.0.1 30 Aug 2018 C2 M2 U4 MIT No Details →
3.0.0 04 May 2018 C2 M2 U4 MIT No Details →
2.0.2 22 Jan 2018 C2 M2 U4 MIT No Details →
2.0.1 21 Jan 2018 C2 M2 U4 MIT No Details →
2.0.0 16 Jan 2018 C2 M2 U4 MIT No Details →
1.4.0 01 Sep 2017 C2 M2 U4 MIT No Details →
1.3.2 30 May 2017 C2 M2 U4 MIT No Details →
1.3.1 02 Sep 2016 C3 M2 U5 MIT No Details →
1.3.0 01 Sep 2016 C3 M2 U5 MIT No Details →
1.2.0 27 Jul 2016 C3 M2 U5 MIT No Details →
1.1.0 22 Jul 2016 C3 M2 U5 MIT No Details →
1.0.0 23 Jun 2016 C3 M2 U5 MIT No Details →
0.7.0 15 Jun 2016 C3 M2 U5 MIT No Details →
0.6.2 01 Jun 2016 C3 M2 U5 MIT No Details →
0.6.1 02 Mar 2016 C3 M2 U5 MIT No Details →
0.5.6 22 Jan 2016 C3 M2 U5 MIT No Details →
0.5.5 05 Jan 2016 C3 M2 U5 MIT No Details →
0.5.4 24 Nov 2015 C3 M2 U5 MIT No Details →
0.5.3 11 Nov 2015 C3 M2 U5 MIT No Details →
0.5.2 17 Sep 2015 C3 M2 U5 MIT No Details →
0.5.1 07 Sep 2015 C3 M2 U5 MIT No Details →
0.5.0 07 Sep 2015 C3 M2 U5 MIT No Details →
0.4.0 14 Aug 2015 C3 M2 U5 MIT No Details →
0.3.0 17 May 2015 C3 M2 U5 MIT No Details →
0.2.0 29 Apr 2015 C3 M2 U5 MIT No Details →
0.1.8 26 Apr 2015 C3 M2 U5 MIT No Details →
0.1.7 26 Apr 2015 C3 M2 U5 MIT No Details →
0.1.6 26 Apr 2015 C3 M2 U5 MIT No Details →
0.1.5 24 Apr 2015 C3 M2 U5 MIT No Details →
0.1.4 23 Apr 2015 C3 M2 U5 MIT No Details →
0.1.3 22 Apr 2015 C3 M2 U5 MIT No Details →
0.1.2 22 Apr 2015 C3 M2 U5 MIT No Details →
0.1.1 22 Apr 2015 C3 M2 U5 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2022 1
  • 2024 4
  • 2025 2
  • 2026 2

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 python-jose

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2016-7036: python-jose failure to use a constant time comparison for HMAC keys 9.8 critical 1.3.2 17 May 2022
CVE-2024-33663: python-jose Critical Vulnerability in HMAC Initialization 9.1 critical No fix published 03 Sep 2026
CVE-2024-33663: python-jose Algorithm Confusion Guard Bypass via DER-Encoded Public Keys 9.1 critical No fix published 15 Oct 2026
CVE-2024-33663: python-jose algorithm confusion with OpenSSH ECDSA keys 7.4 critical 3.4.0 26 Apr 2024
CVE-2024-33664: python-jose Denial of Service via Compressed JWT Tokens 5.3 medium 3.4.0 26 Apr 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: 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 python-jose

Is python-jose safe to use?

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

What is python-jose's Vulert package health score?

Vulert scores python-jose 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 python-jose affected?

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

How many vulnerabilities does python-jose have?

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

4 vulnerabilities were recorded for python-jose in the last 12 months, and the oldest entry in this database dates to 23 Jan 2017. 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-jose 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-jose for upcoming vulnerabilities?

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