CVE-2026-49272

Description

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
HIGH
CVSS v3
8.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N · source cna
Exploit chance (EPSS)
0.328%
chance of exploitation in the next 30 days
higher than 26.3% of scored CVEs · 2026-11-18
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableno
Technical impactpartial
Scored2026-11-05

Timeline

  1. 2026-10-27GitHub advisory published (GHSA-3jp2-3mrg-2vxc)9 days before publication
  2. 2026-11-05Published by the CNA20:58 UTC
  3. 2026-11-05CISA SSVC decision recordedsame day

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-3jp2-3mrg-2vxc, affected packages:

PackageVulnerable versionsFixed in
PyPI oauthlibfrom 3.3.0 before 4.0.14.0.1

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
oauthlib oauthlib

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources