Project Subscriptions
No data.
No advisories yet.
Solution
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.
Workaround
No workaround given by the vendor.
Thu, 19 Nov 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Front-Channel Parameter Handling in Okta Client SDK for Python | |
| Weaknesses | CWE-522 CWE-598 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Okta
Published:
Updated: 2026-11-19T21:04:36.278Z
Reserved: 2026-11-16T21:38:32.395Z
Link: CVE-2026-130153
No data.
Status : Received
Published: 2026-11-19T21:17:53.083
Modified: 2026-11-19T21:17:53.083
Link: CVE-2026-130153
No data.
OpenCVE Enrichment
No data.