Is oauthlib 4.0 vulnerable?

PyPI · 2 releases from 4.0.0 to 4.0.1 · latest oauthlib is 4.0.1 · checked 18 Nov 2026

No known advisories in the last release

oauthlib 4.0.1, the last 4.0 release, has no known advisories. 1 advisory affects earlier 4.0.x releases, so update to 4.0.1.

Update within 4.0:pip install 'oauthlib>=4.0.1'

Is your project on an affected oauthlib?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 4.0.x, affecting earlier releases

  • HighCVE-2026-49272GHSA-3jp2-3mrg-2vxc27 Oct 2026

    OAuthLib: Bearer token can be retrieved as long as client knows a valid client ID for device workflow

    Affected
    >=3.3.0 <4.0.1
    Fixed in
    4.0.1

Every oauthlib 4.0.x release

Affected: 4.0.0. 4.0.1 is not affected.

VersionKnown advisories
oauthlib 4.0.1None
oauthlib 4.0.0CVE-2026-49272

Which of your client projects are still on oauthlib 4.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact oauthlib version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other oauthlib versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.