Skip to main content
VulnerabilityPublished Updated

CVE-2026-49272: OAuthLib · Bearer token can be retrieved as long as client knows a valid client ID for device workflow

Affects prowlerSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.5 High.

Data as of 3 Nov 2026, 04:33 UTC

CVSS 3.1 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Homebrewprowlerpkg:brew/prowlerOther threatsAffected
  • >=5.7.5
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 be cautious when enabling the device workflow grant type and consider additional validation or monitoring controls. Implementations should ensure that device_code parameters are properly validated according to RFC 8628. Follow official OAuthLib advisories for updates and patches.

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 properly, allowing an attacker who knows a valid client ID to obtain a bearer token without a valid device_code. This affects OAuthLib versions 5.7.5 and later. The flaw arises because DeviceCodeGrant.validate_token_request does not check the validity of the device_code, unlike other grant types. This can lead to unauthorized token issuance for clients using the device workflow.

References

Community reviews

Loading reviews…