VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

oauth2: vulnerability history, versions and safety

oauth2 is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 30 releases, from May 2014 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M1 U2
i
1 with no fix published

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

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

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all oauth2 vulnerabilities

Vulert verdict on oauth2 1.9.0.post1 i

Updated on 23 Oct 2026

Careful: 1.9.0.post1 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 Slowing
  • 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 1.9.0.post1 — affected i
  • Vulnerabilities on record 4 over 7 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Depended on by 48 packages i
  • Stars 3,007 i
  • OpenSSF scorecard 2/10 i
  • Last release 133 months ago i
  • Licence MIT 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 oauth2, 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.0.post1 12 Sep 2015 H1 MIT No Details →
1.9.0rc1 17 Aug 2015 H1 MIT No Details →
1.5.211 13 Dec 2011 H1 M1 U2 MIT No Details →
1.5.210 09 Dec 2011 H1 M1 U2 MIT No Details →
1.5.170 03 May 2011 H1 M1 U2 MIT No Details →
1.5.169 15 Apr 2011 H1 M1 U2 MIT No Details →
1.5.168 06 Apr 2011 H1 M1 U2 MIT No Details →
1.5.167 17 Feb 2011 H1 M1 U2 MIT No Details →
1.5.166 15 Feb 2011 H1 M1 U2 MIT No Details →
1.5.165 07 Feb 2011 H1 M1 U2 MIT No Details →
1.5.164 07 Feb 2011 H1 M1 U2 MIT No Details →
1.5.163 04 Feb 2011 H1 M1 U2 MIT No Details →
1.5.162 04 Feb 2011 H1 M1 U2 MIT No Details →
1.5.161 03 Feb 2011 H1 M1 U2 MIT No Details →
1.5.160 03 Feb 2011 H1 M1 U2 MIT No Details →
1.5.159 03 Feb 2011 H1 M1 U2 MIT No Details →
1.5.158 02 Feb 2011 H1 M1 U2 MIT No Details →
1.5.155 02 Feb 2011 H1 M1 U2 MIT No Details →
1.5.153 01 Feb 2011 H1 M1 U2 MIT No Details →
1.5.150 27 Jan 2011 H1 M1 U2 MIT No Details →
1.2.0 14 May 2010 H1 M1 U2 MIT No Details →
1.1.3 27 Mar 2010 H1 M1 U2 MIT No Details →
1.1.1 11 Mar 2010 H1 M1 U2 MIT No Details →
1.1.0 11 Mar 2010 H1 M1 U2 MIT No Details →
1.0.9 09 Mar 2010 H1 M1 U2 MIT No Details →
1.0.8 08 Mar 2010 H1 M1 U2 MIT No Details →
1.0.7 15 Feb 2010 H1 M1 U2 MIT No Details →
1.0.6 12 Feb 2010 H1 M1 U2 MIT No Details →
1.0.0 21 Oct 2009 H1 M1 U2 MIT No Details →
1.0.6.macosx-10.6-universal — H1 M1 U2 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 2
  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for oauth2

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Replay Attack Vulnerability in SimpleGeo python-oauth2 7.5 high No fix published 17 May 2022
CVE-2013-4347: Weak Random Number Generation in oauth2 3.7 medium 1.9rc1 17 May 2022
CVE-2013-4346: oauth2 Replay Attack Vulnerability N/A unrated 1.9rc1 20 May 2014
CVE-2013-4347: Weak Random Number Generation in oauth2 N/A unrated 1.9rc1 20 May 2014

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 oauth2

Is oauth2 safe to use?

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

What is oauth2's Vulert package health score?

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

Yes. 1.9.0.post1, 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 oauth2 should I use?

1.9.0.post1 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 oauth2 have?

4 vulnerabilities are recorded for oauth2 in the PyPI ecosystem: 0 critical, 1 high, 1 medium and 0 low, plus 2 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 oauth2 vulnerabilities disclosed?

0 vulnerabilities were recorded for oauth2 in the last 12 months, and the oldest entry in this database dates to 20 May 2014. 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 oauth2 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 oauth2 for upcoming vulnerabilities?

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