Skip to content
Connect AISign inSign up free
CVE-2026-1301534.7Medium

CVE-2026-130153: Front-Channel Parameter Handling in Okta Client SDK for Python

Okta · Okta Client SDK for Python

Vendor fix available · Affected: Okta Client SDK for Python · Exploitation: not established

At a glance

No EPSS score yet. The score appears once FIRST publishes it.

4.7MediumCVSS
LowMedium

What it isNVD

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.

ExploitationNot established

Not in CISA KEV as of catalogue 2026.11.18 (18 Nov)

  1. Not establishedNothing in the sources we check

Not seen so far: in CISA KEV · exploited (reported) · scanning observed · proof of concept public.

Weakness and public checks

Public check
No public nuclei template
Weakness
Use of HTTP Request With Sensitive Query String · Information Disclosure

Other CVEs in Okta Client SDK for Python

Every published CVE for Okta Okta Client SDK for Python, by how far exploitation has gone. This one is among them.

As a list
Other CVEs in Okta Client SDK for Python: each mark is one CVE.Drag to move · Ctrl + scroll to zoom · a mark opens that CVE

Coverage1 article · 1 outlet

First in our coverage: SecurityOnline, 20 Nov.

  1. Okta patches eight vulnerabilities across SDKs and tools
    SecurityOnline · first in our coverage · mentions it in passing

New articles also arrive in the RSS feed.

References