CVE-2026-130153: Okta Client SDK for Python · Use of GET Request Method With Sensitive Query Strings
Affects Okta Client SDK for PythonSource CVE Database V5
Not known to be exploited · CVSS 4.7 Medium : upgrade to 0.3.1 when convenient.
Data as of 19 Nov 2026, 21:34 UTC
Thin evidence
One scorer or none| CNA (Okta) | CVSS 3.1 | 4.7 |
|---|
- Patch
- Available – fixed in 0.3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 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 19 Nov 2026.
What to do
Upgrade Okta Client SDK for Python to 0.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OktaOkta Client SDK for Python | Affected
| Fixed in
|
AI-suggested
Upgrade the Okta Client SDK for Python to version 0.3.1 or later, where this issue is fixed. No other mitigation is required as the fix addresses the vulnerability directly.
Description
CVE-2026-130153 affects the Okta Client SDK for Python versions 0.1.0 up to but not including 0.3.1. The vulnerability involves the inclusion of sensitive client authentication values, such as client_secret or JWT assertions, as query parameters in GET requests during the authorization code flow when Pushed Authorization Requests (PAR) are not used or fail. This can expose sensitive information in front-channel URLs. The issue has been fixed in version 0.3.1.