VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

authlib: vulnerability history, versions and safety

authlib is a package in the PyPI ecosystem. Vulert records 28 vulnerabilities for it across 59 releases, from Jun 2024 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
28 vulnerabilities recorded C1 H6 M5 U16
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
23 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 authlib vulnerabilities

Vulert verdict on authlib 1.9.1 i

Updated on 23 Oct 2026

Good news: 1.9.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 28.

Package health score 65/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on 1.9.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.9.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.9.1 — unaffected i
  • Vulnerabilities on record 28 over 2 years · 23 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 9,722 packages i
  • Stars 5,441 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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 authlib, 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.9.1 14 Oct 2026 none BSD-3-Clause — Details →
1.9.0 14 Oct 2026 none BSD-3-Clause — Details →
1.8.0 30 Aug 2026 none BSD-3-Clause — Details →
1.7.2 06 May 2026 none BSD-3-Clause — Details →
1.6.12 04 May 2026 none BSD-3-Clause — Details →
1.7.1 04 May 2026 none BSD-3-Clause — Details →
1.7.0 18 Apr 2026 M1 BSD-3-Clause Yes Details →
1.6.11 16 Apr 2026 U1 BSD-3-Clause Yes Details →
1.6.10 13 Apr 2026 M1 U2 BSD-3-Clause Yes Details →
1.6.9 02 Mar 2026 M2 U3 BSD-3-Clause Yes Details →
1.6.8 14 Feb 2026 C1 H2 M2 U6 BSD-3-Clause Yes Details →
1.6.7 06 Feb 2026 C1 H2 M2 U6 BSD-3-Clause Yes Details →
1.6.6 12 Dec 2025 C1 H3 M2 U11 BSD-3-Clause Yes Details →
1.6.5 02 Oct 2025 C1 H3 M3 U12 BSD-3-Clause Yes Details →
1.6.4 17 Sep 2025 C1 H3 M4 U13 BSD-3-Clause Yes Details →
1.6.3 26 Aug 2025 C1 H4 M4 U14 BSD-3-Clause Yes Details →
1.6.2 23 Aug 2025 C1 H4 M4 U14 BSD-3-Clause Yes Details →
1.6.1 20 Jul 2025 C1 H4 M4 U14 BSD-3-Clause Yes Details →
1.6.0 23 May 2025 C1 H4 M4 U14 BSD-3-Clause Yes Details →
1.5.2 02 Apr 2025 C1 H4 M4 U14 BSD-3-Clause Yes Details →
1.5.1 28 Feb 2025 C1 H4 M4 U14 BSD-3-Clause Yes Details →
1.5.0 25 Feb 2025 C1 H4 M4 U14 BSD-3-Clause Yes Details →
1.4.1 28 Jan 2025 C1 H4 M4 U14 BSD-3-Clause Yes Details →
1.4.0 20 Dec 2024 C1 H4 M4 U14 BSD-3-Clause Yes Details →
1.3.2 26 Aug 2024 C1 H4 M4 U14 BSD-3-Clause Yes Details →
1.3.1 04 Jun 2024 C1 H4 M4 U14 BSD-3-Clause Yes Details →
1.3.0 17 Dec 2023 C1 H5 M4 U15 BSD-3-Clause Yes Details →
1.2.1 25 Jun 2023 C1 H5 M4 U15 BSD-3-Clause Yes Details →
1.2.0 06 Dec 2022 C1 H5 M4 U15 BSD-3-Clause Yes Details →
0.15.6 01 Nov 2022 C1 H5 M4 U14 BSD-3-Clause Yes Details →
1.1.0 13 Sep 2022 C1 H5 M4 U15 BSD-3-Clause Yes Details →
1.0.1 06 Apr 2022 C1 H5 M4 U15 BSD-3-Clause Yes Details →
1.0.0 15 Mar 2022 C1 H5 M4 U15 BSD-3-Clause Yes Details →
1.0.0rc1 14 Jan 2022 C1 H5 M4 U14 BSD-3-Clause Yes Details →
1.0.0b2 27 Oct 2021 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.15.5 18 Oct 2021 C1 H5 M4 U14 BSD-3-Clause Yes Details →
1.0.0b1 09 Sep 2021 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.15.4 05 Jun 2021 C1 H5 M4 U14 BSD-3-Clause Yes Details →
1.0.0a2 05 Jun 2021 C1 H5 M4 U14 BSD-3-Clause Yes Details →
1.0.0a1 31 Jan 2021 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.15.3 15 Jan 2021 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.15.2 18 Oct 2020 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.15.1 14 Oct 2020 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.15.0 10 Oct 2020 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.14.3 18 May 2020 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.14.2 06 May 2020 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.14.1 12 Feb 2020 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.14.0 11 Feb 2020 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.13.0 11 Nov 2019 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.12.1 12 Sep 2019 C1 H5 M4 U14 BSD-3-Clause Yes Details →
0.12.0 03 Sep 2019 C1 H5 M4 U14 non-standard Yes Details →
0.11.0 06 Apr 2019 C1 H5 M4 U14 non-standard Yes Details →
0.10.0 12 Oct 2018 C1 H5 M4 U14 non-standard Yes Details →
0.9.0 12 Aug 2018 C1 H5 M4 U14 non-standard Yes Details →
0.8.0 17 Jun 2018 C1 H5 M4 U14 non-standard Yes Details →
0.7.0 28 Apr 2018 C1 H5 M4 U14 non-standard Yes Details →
0.6.0 20 Mar 2018 C1 H5 M4 U14 LGPL-3.0 Yes Details →
0.5.1 11 Feb 2018 C1 H5 M4 U14 LGPL-3.0 Yes Details →
0.5.0 11 Feb 2018 C1 H5 M4 U14 LGPL-3.0 Yes Details →
0.4.1 01 Feb 2018 C1 H5 M4 U14 LGPL-3.0 Yes Details →
0.4.0 31 Jan 2018 C1 H5 M4 U14 LGPL-3.0 Yes Details →
0.3.0 24 Dec 2017 C1 H5 M4 U14 LGPL-3.0 Yes Details →
0.2.1 06 Dec 2017 C1 H5 M4 U14 LGPL-3.0 Yes Details →
0.2.0 25 Nov 2017 C1 H5 M4 U14 LGPL-3.0 Yes Details →
0.1.0 18 Nov 2017 C1 H5 M4 U14 LGPL-3.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2
  • 2025 3
  • 2026 23

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

03 Vulnerabilities

Recorded vulnerabilities for authlib

The 5 most severe of 28 vulnerabilities recorded for this package

Search all 28 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-28802: Authlib Package Vulnerability Allows Malicious JWT Signature Bypass 9.8 critical 1.6.7 06 Mar 2026
CVE-2026-27962: Authlib JWS JWK Header Injection Vulnerability Leading to Signature Verification Bypass 9.1 critical 1.6.9 29 Jun 2026
CVE-2026-27962: Authlib JWS JWK Header Injection Vulnerability Leading to Signature Verification Bypass 9.1 critical 1.6.9 16 Mar 2026
CVE-2026-28490: Authlib Vulnerable to JWE RSA1_5 Bleichenbacher Padding Oracle 8.3 high 1.6.9 16 Mar 2026
CVE-2026-28498: Authlib Critical Fail-Open Vulnerability in OIDC Hash Binding 8.2 high 1.6.9 16 Mar 2026

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 authlib

Is authlib safe to use?

Vulert records 28 vulnerabilities for authlib in PyPI: 1 critical, 6 high, 5 medium and 0 low, plus 16 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.

What is authlib's Vulert package health score?

Vulert scores authlib 65/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).

Is the latest version of authlib affected?

No. 1.9.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of authlib should I use?

1.9.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 authlib have?

28 vulnerabilities are recorded for authlib in the PyPI ecosystem: 1 critical, 6 high, 5 medium and 0 low, plus 16 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 authlib vulnerabilities disclosed?

23 vulnerabilities were recorded for authlib in the last 12 months, and the oldest entry in this database dates to 09 Jun 2024. 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 authlib 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 authlib for upcoming vulnerabilities?

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