OAuthLib is an implementation of the OAuth request-signing logic for Python 3.6+. Prior to 4.0.0, the client_credentials and Resource Owner Password Credentials token grant handlers can authenticate request.client as one confidential client while retaining an attacker-supplied request.client_id for validate_grant_type and validate_scopes. A lower-privilege authenticated client can therefore cause grant and scope authorization to use another client's identity when an application validator relies on the documented client_id argument, potentially issuing tokens with unauthorized grants or scopes. Validators that authorize exclusively from request.client may not be affected. This issue is fixed in version 4.0.0.
CVE-2026-118669
HIGHPre-NVD 8.48.4ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (24th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-112488 (ENISA EUVD) · GHSA-7984-qgvg-3j9c (GitHub Security Advisories)Source: ENISA EUVD
8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.4Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS
- 8.4
- EG Score
- 8.4HIGHmedium confidence
- EG Risk
- 54EG Risk 54/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity84% × 45%Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 24th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 28, 2026
Last Modified
November 3, 2026
Advisory Details (4)
Auto-updated Oct 28, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github, github_pr.
GitHub release Patch Available
4.0.0
Patch available: oauthlib/oauthlib v4.0.0
https://github.com/oauthlib/oauthlib/releases/tag/v4.0.0GitHub commit Patch Available
commit c951a1d09f99 (oauthlib/oauthlib)
Patch available: oauthlib/oauthlib v4.0.0 (contains commit c951a1d09f99)
https://github.com/oauthlib/oauthlib/commit/c951a1d09f99f14e3240973fa83c4f4287d4753dGitHub pull request Patch Available
Fix client authentication for DeviceCodeGrant when getting a token
Patch available: oauthlib/oauthlib v4.0.0 (PR #920 merged 2026-07-14)
https://github.com/oauthlib/oauthlib/pull/920GitHub advisoryMentions a patch (unverified)🟡 PoC Available
Token grants can use attacker-supplied client_id for authorization after authenticating a different client · Advisory · oauthlib/oauthlib · GitHub
https://github.com/oauthlib/oauthlib/security/advisories/GHSA-7984-qgvg-3j9cVendor Advisories for CVE-2026-118669(14)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:99167Red Hat Product SecurityHigh
Red Hat Security Advisory: python-oauthlib security update
- RHSA-2026:99027Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Quay - 3.12.24
- RHSA-2026:99026Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Quay - 3.17.7
- RHSA-2026:99025Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Quay - 3.10.28
- RHSA-2026:99024Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Quay - 3.14.10
- RHSA-2026:99023Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Quay - 3.15.9
- RHSA-2026:99022Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Quay - 3.16.7
- RHSA-2026:99021Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Quay - 3.9.28
- +6 more
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | discovery/discovery-server-rhel9:1793734080 | 2026-11-04 | redhat |
| pip | oauthlib @ 4.0.0 (fixes < 4.0.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-oauthlib | 3.2.2-1 ... 3.3.1-2 (6 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-oauthlib | 3.2.2-3, 3.2.2-4, 3.3.1-1, 3.3.1-2 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-oauthlib | 3.2.2-3, 3.2.2-4, 3.3.1-1, 3.3.1-2 |
| — |
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| oauthlib | 0.0.1 ... 3.3.1 (52 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 26× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-11 03:44 UTCEchelonGraph re-scored
- 2026-11-11 03:44 UTCVendor advisory
- 2026-11-11 03:44 UTCGHSA enrichmentGHSA-7984-qgvg-3j9c · GitHub severity HIGH
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-03 20:14 UTCEchelonGraph re-scored
- 2026-11-03 20:14 UTCVendor advisory
- 2026-11-03 20:14 UTCGHSA enrichmentGHSA-7984-qgvg-3j9c · GitHub severity HIGH
- 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-03 14:29 UTCEchelonGraph re-scored
- 2026-11-03 14:29 UTCVendor advisory
- 2026-11-03 14:29 UTCGHSA enrichmentGHSA-7984-qgvg-3j9c · GitHub severity HIGH
- 2026-11-03 13:43 UTCEchelonGraph re-scored
- 2026-11-03 13:43 UTCVendor advisory
- 2026-11-03 13:43 UTCGHSA enrichmentGHSA-7984-qgvg-3j9c · GitHub severity HIGH
- 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
Show 7 moreShow fewer
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-28 22:26 UTCEchelonGraph re-scored
- 2026-10-28 22:01 UTCENISA EUVD ID recordedEUVD-2026-112488 · Source: ENISA EUVD
- 2026-10-28 21:20 UTCEchelonGraph re-scoredFirst assessed: 8.4 HIGH
- 2026-10-28 21:18 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same vendor + same CWE)
Same product
4 shownDebian:12:python-oauthlib
Same vendor
10 shownredhat:RHSA-2026:94802
Frequently asked(5)
What is CVE-2026-118669?
CVE-2026-118669 is a high-severity vulnerability; its CVE record was published on October 28, 2026. OAuthLib is an implementation of the OAuth request-signing logic for Python 3.6+. Prior to 4.0.0, the client_credentials and Resource Owner Password Credentials token grant handlers can authenticate request.client as one confidential client while retaining an attacker-supplied request.client_id for…
When was the CVE record for CVE-2026-118669 published?
The CVE record for CVE-2026-118669 was published on October 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-118669 actively exploited?
CVE-2026-118669 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118669?
CVE-2026-118669 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-118669?
A fix for CVE-2026-118669 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-118669 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-118669
Is Your Infrastructure Affected by CVE-2026-118669?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.