cve.bz

CVE-2026-49272 oauthlib oauthlib: Improper Authentication

8.5 highEPSS 0.3%Fix available

High (8.5) in oauthlib oauthlib. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in oauthlib 4.0.1.

On this page
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.

Severity

CVSS 3.1

8.5 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
oauthlib>= 3.3.0, < 4.0.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3jp2-3mrg-2vxcPyPIoauthlib>=3.3.0 <4.0.14.0.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14python-oauthlibno fix listedDEBIAN-CVE-2026-49272
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morepython-oauthlibno fix listedUBUNTU-CVE-2026-49272
openSUSETumbleweedpython-oauthlib4.0.1-1.1openSUSE-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

Red Hat rates this Important.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat OpenShift AI (RHOAI)rhoai/odh-mlflow-rhel9Not 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.

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON