CVE-2026-49272: OAuthLib · Bearer token can be retrieved as long as client knows a valid client ID for device workflow
Affects rockcraftSource GCVE Database
Not known to be exploited · CVSS 8.5 High.
Data as of 3 Nov 2026, 04:33 UTC
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewrockcraftpkg:brew/rockcraftOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, users should review their OAuthLib implementation to ensure that device_code validation is properly enforced in the DeviceCodeGrant.validate_token_request method and that public clients are authenticated securely. Implementing a validate_device_code method in RequestValidator and invoking it during token request validation is recommended to comply with RFC 8628.
Description
OAuthLib contains a vulnerability in its implementation of the OAuth 2.0 device authorization grant (RFC 8628). Specifically, the token endpoint does not validate the device_code parameter, allowing an attacker who knows a valid client ID for a public client using the device workflow to obtain a bearer token without a valid device_code. This flaw arises because DeviceCodeGrant.validate_token_request lacks proper device_code validation and mishandles public clients.