Vulnerability Database · PyPI · oauthlib · Version
oauthlib 2.0.5
2.0.5 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 4.0.0.
Critical 0 High 0 Medium 2 Low 0 Unrated 0
-
Released 18 Oct 2017
Licence non-standard
Also known from other sources 2
Newer releases 52
Database updated 23/Oct/2026
Release and licence data published by PyPI. 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 Vulnerabilities affecting this version
oauthlib 2.0.5 vulnerabilities
2 vulnerabilities cover oauthlib 2.0.5. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-49264: oauthlib - Unsafe JSONP Callback Injection in RevocationEndpoint | 6.1 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 |
Looking for another version, or everything Vulert holds for oauthlib?
Questions
About oauthlib 2.0.5
Is oauthlib 2.0.5 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover oauthlib 2.0.5: 0 critical, 0 high, 2 medium and 0 low. The upgrade Vulert recommends is 4.0.0, and each entry above names the fixed version to move to.
Which version of oauthlib should I use instead of 2.0.5?
4.0.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 2.0.5 the latest release of oauthlib?
No. 2.0.5 was published 18 Oct 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.