CVSS 3.1
8.5 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:NHigh (8.5) in oauthlib oauthlib. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in oauthlib 4.0.1.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:Noauthlib (PyPI): fixed in 4.0.1Explain CVE-2026-49272 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-49272?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-49272?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-49272 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| oauthlib | >= 3.3.0, < 4.0.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-3jp2-3mrg-2vxc | PyPI | oauthlib | >=3.3.0 <4.0.1 | 4.0.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | python-oauthlib | no fix listed | DEBIAN-CVE-2026-49272 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS and 4 more | python-oauthlib | no fix listed | UBUNTU-CVE-2026-49272 |
| openSUSE | Tumbleweed | python-oauthlib | 4.0.1-1.1 | openSUSE-SU-2026:12520-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.
Red Hat rates this Important.
This vulnerability is rated as Important because a remote attacker with knowledge of a registered client identifier can bypass authentication mechanisms to acquire valid bearer tokens. Exploitation requires the authorization server to support and actively expose the RFC 8628 device authorization grant workflow. Deployments where the device authorization flow is not implemented or enabled are not susceptible to this flaw.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
--- CME Mitigation Guidance (2026-11-06) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to enforce presence and validation of the device_code parameter in DeviceCodeGrant.validate_token_request before issuing tokens: upgrade to OAuthLib 4.0.1 (or the fixed Rhoai/Odh Mlflow Rhel builds), which require device_code presence in DeviceCodeGrant.validate_token_request and delegate code verification and authorization state checks to RequestValidator.validate_device_code, closing all 2 injection vectors (token request with a bogus device_code parameter, token request with a missing device_code parameter). Until patched, this is only a concern on OAuthLib authorization servers implementing and exposing the RFC 8628 device authorization workflow — Deployments where the RFC 8628 device authorization flow is not implemented or enabled are unaffected — so disable the RFC 8628 device authorization grant workflow or restrict network access to the token endpoint and monitor token requests using client IDs registered for device authorization. These controls limit blast radius and contain exploitation, but they do not fix the underlying missing device code validation flaw — apply the upstream patch to fully remediate.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-mlflow-rhel9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-49272.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.