OAuthLib: Token grants can use attacker-supplied client_id for authorization after authenticating a different client — GHSA-7984-QGVG-3J9C
GitHub · GitHub · GHSA-7984-QGVG-3J9C
ID
GHSA-7984-QGVG-3J9C
GHSA-7984-QGVG-3J9C
Date
Source
GitHub
GitHub
Vendor
GitHub
GitHub
Threat
high
high
CVSS
8.4
8.4
EPSS
0.00312
0.00312
Summary
## Summary OAuthlib's token grant handlers can authenticate one client while authorizing the grant type and requested scopes using a different, attacker-supplied `client_id` from the request body. In affected token grant flows, `authenticate_client(request)` sets `request.client` to the authenticated client object, but OAuthlib does not require `request.client_id` to match `request.client.client_id`. If the request…
Timeline
- Published by source
- 2026-10-30
Risk context
- Reported severity or threat level: high.
- Reported CVSS score: 8.4 out of 10.
- Reported EPSS value: 0.00312.
- Review exposure for the affected product or family: pip: oauthlib.
Product
pip: oauthlib
What to do
General, cautious steps (verify details in the official source):
- Prioritize patching or mitigation immediately (treat as actively risky).
- Identify affected product versions in your inventory and verify whether you are impacted.
- Apply vendor patches/updates or recommended mitigations as soon as available.
- Read the official advisory for exact affected versions and remediation steps.
Official advisory
Evidence and provenance
- Canonical advisory ID
- GHSA-7984-QGVG-3J9C
- Source
- GitHub
- Vendor
- GitHub
- Published by source
- 2026-10-30
- Last source activity
- 2026-10-30
- Additional identifiers
- CVE-2026-118669
- Curated by
- hlukh.ch
Related advisories and connections
These advisories are connected by shared CVE, product, vendor, source, or time signals.