VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

oauthenticator: vulnerability history, versions and safety

oauthenticator is a package in the PyPI ecosystem. Vulert records 13 vulnerabilities for it across 50 releases, from Feb 2018 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
13 vulnerabilities recorded H6 M1 U6
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 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all oauthenticator vulnerabilities

Vulert verdict on oauthenticator 17.4.0 i

Updated on 23 Oct 2026

Action needed: 17.4.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 64/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 17.4.0 — affected i
  • Vulnerabilities on record 13 over 8 years · 4 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 18 packages i
  • Stars 445 i
  • OpenSSF scorecard 4/10 i
  • Last release 6 months ago i
  • Licence BSD-3-Clause 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 oauthenticator, 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
17.4.0 26 Mar 2026 U1 BSD-3-Clause Yes Details →
17.3.0 11 Dec 2024 H1 U1 non-standard Yes Details →
17.2.0 03 Dec 2024 H1 U1 non-standard Yes Details →
17.1.0 11 Oct 2024 H1 U1 non-standard Yes Details →
17.0.0 04 Sep 2024 H1 U1 non-standard Yes Details →
16.3.1 11 Jun 2024 H1 U1 non-standard Yes Details →
16.3.0 20 Mar 2024 H2 U2 non-standard Yes Details →
16.2.1 27 Nov 2023 H3 U3 non-standard Yes Details →
16.2.0 23 Nov 2023 H3 U3 non-standard Yes Details →
16.1.1 18 Oct 2023 H3 U3 non-standard Yes Details →
16.1.0 28 Sep 2023 H3 U3 non-standard Yes Details →
16.0.7 21 Aug 2023 H3 U3 non-standard Yes Details →
16.0.6 17 Aug 2023 H3 U3 non-standard Yes Details →
16.0.5 15 Aug 2023 H3 U3 non-standard Yes Details →
16.0.4 11 Aug 2023 H3 U3 non-standard Yes Details →
16.0.3 08 Jul 2023 H3 U3 non-standard Yes Details →
16.0.2 06 Jul 2023 H3 U3 non-standard Yes Details →
16.0.1 05 Jul 2023 H3 U3 non-standard Yes Details →
16.0.0 05 Jul 2023 H3 U3 non-standard Yes Details →
15.1.0 08 Sep 2022 H3 U3 non-standard Yes Details →
15.0.1 09 Jun 2022 H3 U3 non-standard Yes Details →
15.0.0 06 Jun 2022 H3 U3 non-standard Yes Details →
14.2.0 10 Aug 2021 H3 M1 U4 non-standard Yes Details →
14.1.0 19 Jul 2021 H3 M1 U4 non-standard Yes Details →
14.0.0 09 Apr 2021 H3 M1 U4 non-standard Yes Details →
0.13.0 04 Feb 2021 H3 M1 U4 non-standard Yes Details →
0.12.3 04 Dec 2020 H3 M1 U4 non-standard Yes Details →
0.12.2 30 Nov 2020 H3 M1 U4 non-standard Yes Details →
0.12.1 20 Nov 2020 H4 M1 U5 non-standard Yes Details →
0.12.0 26 Oct 2020 H4 M1 U5 non-standard Yes Details →
0.11.0 31 Jan 2020 H3 M1 U4 non-standard Yes Details →
0.10.0 27 Nov 2019 H3 M1 U4 non-standard Yes Details →
0.9.0 30 Jul 2019 H3 M1 U4 non-standard Yes Details →
0.8.2 16 Apr 2019 H3 M1 U4 non-standard Yes Details →
0.8.1 28 Feb 2019 H3 M1 U4 non-standard Yes Details →
0.8.0 11 Aug 2018 H3 M1 U4 non-standard Yes Details →
0.7.3 16 Feb 2018 H3 M1 U4 non-standard Yes Details →
0.6.2 16 Feb 2018 H3 M1 U4 non-standard Yes Details →
0.7.2 27 Oct 2017 H3 M1 U5 non-standard Yes Details →
0.7.1 04 Oct 2017 H3 M1 U5 non-standard Yes Details →
0.7.0 03 Oct 2017 H3 M1 U5 non-standard Yes Details →
0.6.1 11 Aug 2017 H5 M1 U5 non-standard Yes Details →
0.6.0 27 Jul 2017 H5 M1 U5 non-standard Yes Details →
0.5.1 05 Oct 2016 H3 M1 U4 non-standard Yes Details →
0.5.0 02 Sep 2016 H3 M1 U4 non-standard Yes Details →
0.4.1 18 May 2016 H3 M1 U4 non-standard Yes Details →
0.4.0 11 May 2016 H3 M1 U4 non-standard Yes Details →
0.3.0 20 Apr 2016 H3 M1 U4 non-standard Yes Details →
0.2.0 04 Jan 2016 H3 M1 U4 non-standard Yes Details →
0.1.0 22 Dec 2015 H3 M1 U4 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2020 2
  • 2022 4
  • 2024 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for oauthenticator

The 5 most severe of 13 vulnerabilities recorded for this package

Search all 13 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-7206: JupyterHub OAuthenticator GitLab Group Whitelisting Bypass 8.8 high 0.6.2 13 May 2022
CVE-2026-33175: OAuthenticator Authentication Bypass Vulnerability 8.8 high 17.4.0 03 Apr 2026
CVE-2026-33175: oauthenticator Authentication Bypass via Unverified Email Claims 8.8 high 17.4.0 03 Apr 2026
CVE-2018-7206: JupyterHub OAuthenticator elevation of privilege 8.8 high 0.6.2 13 May 2022
CVE-2024-37300: oauthenticator - Identity Provider Restriction Bypass in JupyterHub 5.0 8.1 high 16.3.1 07 Jul 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 oauthenticator

Is oauthenticator safe to use?

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

Vulert scores oauthenticator 64/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 oauthenticator affected?

Yes. 17.4.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of oauthenticator should I use?

17.4.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 oauthenticator have?

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

4 vulnerabilities were recorded for oauthenticator in the last 12 months, and the oldest entry in this database dates to 18 Feb 2018. 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 oauthenticator 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 oauthenticator for upcoming vulnerabilities?

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