CVE-2026-49272
OAuthLib is an implementation of the OAuth request-signing logic …
OAuthLib is an implementation of the OAuth request-signing logic for Python 3.6+. From 3.3.0 until 4.0.1, OAuthLib's RFC 8628 device workflow does not require DeviceCodeGrant.validate_token_request to check that the device_code parameter is present and valid. A caller whose client request is accepted by the configured validator and who knows a valid client ID enabled for the device workflow can submit a missing or bogus device code to the token endpoint and obtain a bearer token without completing device authorization. This issue is fixed in version 4.0.1.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/oauthlib/oauthlib/security/advisories/GHSA-3jp2-3mrg-2vxc
- github.com/oauthlib/oauthlib/releases/tag/v4.0.0
- github.com/advisories/GHSA-3jp2-3mrg-2vxc
- github.com/oauthlib/oauthlib/commit/77a5f1c8ce00da2b0b8c5f6e9cc129920085f114
- github.com/oauthlib/oauthlib/pull/954
- github.com/oauthlib/oauthlib/releases/tag/v4.0.1
- nvd.nist.gov/vuln/detail/CVE-2026-49272
- cve.org/CVERecord?id=CVE-2026-49272
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.