Skip to main content
VulnerabilityPublished Updated

CVE-2026-118669: Important · python-oauthlib security update

Affects python3-oauthlibSource GCVE Database

0
Compare
Authoritative record:CVE-2026-118669· High 8.4

Not known to be exploited · CVSS 8.4 High : upgrade to 3.2.2-6.el10_3.1 soon.

Data as of 16 Nov 2026, 18:36 UTC

CVSS 4.0 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.4
Patch
Available – fixed in 3.2.2-6.el10_3.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA: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 15 Nov 2026.

What to do

Upgrade the AlmaLinux python3-oauthlib package to 3.2.2-6.el10_3.1.

Affected software

ProductAffectedFixed in
AlmaLinux 10python3-oauthlibAffected
  • <3.2.2-6.el10_3.1
Fixed in
  • 3.2.2-6.el10_3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A security update fixing this vulnerability is available in python-oauthlib version 3.2.2-6.el10_3.1. Users should apply this update as provided by Red Hat in advisory RHSA-2026:98641. No additional mitigations are specified or required beyond applying the official patch.

Description

A vulnerability in python-oauthlib (CVE-2026-118669) allows a remote authenticated client with low privileges to escalate privileges by exploiting client identity confusion in token grant handlers. The flaw occurs when the authorization system authenticates a client but uses a different client-supplied identifier for permission and scope validation, enabling attackers to obtain access tokens with unauthorized permissions. This affects deployments relying on the submitted client identifier parameter rather than the authenticated client object during scope or grant checks. A fixed version 3.2.2-6.el10_3.1 is available.

References

Community reviews

Loading reviews…