Front-Channel Parameter Handling in Okta Client SDK for Python CVE-2026-130153 - Nov 19, 2026
Description
The Okta Client SDK for Python (okta-client-python) includes client authentication values (client_secret or JWT assertions) as query parameters in the front-channel authorization URL when executing the authorization code flow without Pushed Authorization Requests (PAR). When PAR is disabled, unsupported by the authorization server, or fails, the SDK falls back to standard authorization URL construction, transmitting these parameters via user-agent requests.
Preconditions
An application is configured to authenticate using a client secret or JWT client assertion,
The application initiates an authentication flow using the authorization code grant, and
Pushed Authorization Requests (PAR) are disabled, unsupported by the authorization server, or the initial PAR request fails.
Affected product and versions
Customers using the Okta Client SDK for Python (the okta-client-python PyPI package) versions 0.1.0 through 0.3.0 are affected.
Customer Recommendations
To remediate this vulnerability, upgrade the Okta Client SDK for Python to version 0.3.1 or greater. Customers should also rotate the client secret for any application that has run the authorization code flow without PAR.
Resolution
The vulnerability is present in Okta Client SDK for Python versions 0.1.0 through 0.3.0 and is resolved in version 0.3.1.
CVE details
CVE ID | |
Published Date | 2026-11-19 |
Vulnerability Type | Sensitive Parameter in Query String (CWE-598) |
CWE | CWE-598 (Use of GET Request Method with Sensitive Query Strings) CWE-522 (Insufficiently Protected Credentials) |
CVSS v3 | Score: 4.7 (Medium) Vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N |