Is oauthlib 0.7 vulnerable?
PyPI · 3 releases from 0.7.0 to 0.7.2 · latest oauthlib is 4.0.1 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. oauthlib 0.7.2, the last 0.7 release, is affected by 2 known security advisories (1 high, 1 medium), including CVE-2026-118669, CVE-2026-49264. Upgrade to 4.0.0 or later to fix all of them.
pip install 'oauthlib>=4.0.0'Is your project on an affected oauthlib?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting oauthlib 0.7.2
OAuthLib: Token grants can use attacker-supplied client_id for authorization after authenticating a different client
- Affected
- <4.0.0
- Fixed in
- 4.0.0
Oauthlib : Unsafe JSONP callback injection in RevocationEndpoint allows arbitrary JavaScript response generation
- Affected
- >=0.6.1 <4.0.0
- Fixed in
- 4.0.0
Every oauthlib 0.7.x release
Affected: 0.7.0 to 0.7.2. Latest oauthlib: 4.0.1.
| Version | Known advisories |
|---|---|
| oauthlib 0.7.2 | CVE-2026-118669, CVE-2026-49264 |
| oauthlib 0.7.1 | CVE-2026-118669, CVE-2026-49264 |
| oauthlib 0.7.0 | CVE-2026-118669, CVE-2026-49264 |
Which of your client projects are still on oauthlib 0.7?
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.