VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

oauthlib: vulnerability history, versions and safety

oauthlib is a package in the PyPI ecosystem. Vulert records 6 vulnerabilities for it across 52 releases, from Sep 2022 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
6 vulnerabilities recorded M3 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all oauthlib vulnerabilities

Vulert verdict on oauthlib 4.0.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 4.0.0 — unaffected i
  • Vulnerabilities on record 6 over 4 years · 4 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 6.8 i
  • With no published fix 0 i
  • Depended on by 13,536 packages i
  • Stars 2,988 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence BSD-3-Clause i
  • Similar names authlib 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 oauthlib, 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
4.0.0 28 Sep 2026 none BSD-3-Clause — Details →
3.3.1 19 Jun 2025 M2 U2 BSD-3-Clause Yes Details →
3.3.0 17 Jun 2025 M2 U2 BSD-3-Clause Yes Details →
3.2.2 17 Oct 2022 M2 U2 non-standard Yes Details →
3.2.1 09 Sep 2022 M3 U2 non-standard Yes Details →
3.2.0 29 Jan 2022 M3 U3 non-standard Yes Details →
3.1.1 01 Jun 2021 M3 U3 non-standard Yes Details →
3.1.0 06 Aug 2019 M2 U2 non-standard Yes Details →
3.0.2 04 Jul 2019 M2 U2 non-standard Yes Details →
3.0.1 24 Jan 2019 M2 U2 non-standard Yes Details →
3.0.0 08 Jan 2019 M2 U2 non-standard Yes Details →
2.1.0 22 May 2018 M1 U1 non-standard Yes Details →
2.0.7 19 Mar 2018 M1 U1 non-standard Yes Details →
2.0.6 19 Oct 2017 M1 U1 non-standard Yes Details →
2.0.5 18 Oct 2017 M1 U1 non-standard Yes Details →
2.0.4 17 Sep 2017 M1 U1 non-standard Yes Details →
2.0.3 07 Sep 2017 M1 U1 non-standard Yes Details →
2.0.2 19 Mar 2017 M1 U1 non-standard Yes Details →
2.0.1 23 Nov 2016 M1 U1 non-standard Yes Details →
2.0.0 03 Sep 2016 M1 U1 non-standard Yes Details →
1.1.2 01 Jun 2016 M1 U1 non-standard Yes Details →
1.1.1 01 May 2016 M1 U1 non-standard Yes Details →
1.0.3 16 Aug 2015 M1 U1 non-standard Yes Details →
1.0.2 16 Aug 2015 M1 U1 non-standard Yes Details →
1.0.1 28 Jul 2015 M1 U1 non-standard Yes Details →
1.0.0 20 Jul 2015 M1 U1 non-standard Yes Details →
0.7.2 13 Nov 2014 M1 U1 non-standard Yes Details →
0.7.1 27 Oct 2014 M1 U1 non-standard Yes Details →
0.7.0 27 Oct 2014 M1 U1 non-standard Yes Details →
0.6.3 10 Jun 2014 M1 U1 non-standard Yes Details →
0.6.2 06 Jun 2014 M1 U1 non-standard Yes Details →
0.6.1 20 Jan 2014 M1 U1 non-standard Yes Details →
0.6.0 13 Sep 2013 U1 non-standard Yes Details →
0.5.1 26 Jul 2013 U1 non-standard Yes Details →
0.5.0 09 Jul 2013 U1 non-standard Yes Details →
0.4.2 31 May 2013 U1 non-standard Yes Details →
0.4.1 20 May 2013 U1 non-standard Yes Details →
0.4.0 26 Mar 2013 U1 non-standard Yes Details →
0.3.8 23 Feb 2013 U1 non-standard Yes Details →
0.3.7 11 Feb 2013 U1 non-standard Yes Details →
0.3.6 04 Feb 2013 U1 non-standard Yes Details →
0.3.5 29 Jan 2013 U1 non-standard Yes Details →
0.3.4 19 Nov 2012 U1 — Yes Details →
0.3.3 08 Nov 2012 U1 — Yes Details →
0.3.2 08 Nov 2012 U1 — Yes Details →
0.3.0 13 Aug 2012 U1 — Yes Details →
0.1.3 06 May 2012 U1 — Yes Details →
0.1.2 03 May 2012 U1 — Yes Details →
0.1.1 03 May 2012 U1 — Yes Details →
0.1.0 03 May 2012 U1 — Yes Details →
0.0.2 12 Apr 2012 U1 — Yes Details →
0.0.1 11 Apr 2012 U1 — Yes Details →
1.1.0.post1 — M1 U2 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for oauthlib

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-49265: Oauthlib Timing Attack Vulnerability in PKCE Code Verifier Comparison 6.8 medium 4.0.0 29 Sep 2026
CVE-2026-49265: Oauthlib Timing Attack Vulnerability in PKCE Code_Verifier Comparison 6.8 medium 4.0.0 01 Oct 2026
CVE-2026-49264: oauthlib Unsafe JSONP Callback Injection Vulnerability 6.1 medium 4.0.0 29 Sep 2026
CVE-2026-49264: oauthlib - Unsafe JSONP Callback Injection in RevocationEndpoint 6.1 medium 4.0.0 01 Oct 2026
CVE-2022-36087: OAuthLib DoS Vulnerability 5.7 medium 3.2.2 16 Sep 2022

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 oauthlib

Is oauthlib safe to use?

Vulert records 6 vulnerabilities for oauthlib in PyPI: 0 critical, 0 high, 3 medium and 0 low, plus 3 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 oauthlib's Vulert package health score?

Vulert scores oauthlib 85/100, which reads as healthy. 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 oauthlib affected?

No. 4.0.0, 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 oauthlib should I use?

4.0.0 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 oauthlib have?

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

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

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