Okta Client SDK for Python secret disclosure in authorization URLs
- Exploited
- No known exploitation
- Fix
- Fixed in 0.3.1
- Who is exposed
- Not reported
Summary
The Okta Client SDK for Python sends client secrets or JWT assertions as query parameters in front-channel authorization URLs when Pushed Authorization Requests (PAR) are disabled, unsupported, or fail, so those values travel through the user's browser. An attacker can remotely, without logging in, but needs the user to take an action to read some of those authentication values.
Written by a model
Original 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.
What to do
Upgrade to a fixed version: 0.3.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130153 (Front-Channel Parameter Handling in Okta Client SDK for Python), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130153 (entry last updated 2026-11-19):
Affected:
- Okta Okta Client SDK for Python: from 0.1.0, fixed in 0.3.1
Fixed versions: 0.3.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130153 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130153 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://trust.okta.com/security-advisories/front-channel-parameter-handling-in-okta-client-sdk-for-python-cve-2026-130153
- https://github.com/okta/okta-client-python/releases/tag/0.3.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130153
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130153"}.Affected versions
- Okta Okta Client SDK for PythonFrom 0.1.0 · fixed in 0.3.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.7/10CVSS 4.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | trust.okta.com · security-advisories/front-channel-parameter-handling-in-okta-client-sdk-for-python-cve-2026-130153 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130153 |
| Record | NVD · CVE-2026-130153 |
| Other links 1 | |
| Repository | GitHub · okta/okta-client-python · Release 0.3.1 |
Questions about CVE-2026-130153
Is CVE-2026-130153 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-130153?
Okta Client SDK for Python: from 0.1.0 before 0.3.1.
Source: cve.now feed data
How do I fix CVE-2026-130153?
Upgrade to a fixed version: 0.3.1.
Source: cve.now feed data
Related
- CVE-2026-115547Command Execution via Admin Console Input in Okta Access Gateway
- CVE-2026-130235Improper Request URL Validation in the Okta .NET SDK Abstractions Library
- CVE-2026-130236API Authentication and Rule Generation in the Auth0 Authorization Extension
- CVE-2026-130179Credential Overwriting in Okta .NET SDK Abstractions Library
- CVE-2026-130151FreeRDP Smartcard Redirection Memory Handling in Okta Privileged Access Gateway
- CVE-2026-115546Authentication Source Verification Issue in Okta Access Gateway
No corrections so far. Something wrong on this page? Report an error.