Skip to content
Fencer Intel
medium 4.7

CVE-2026-130153 json

Front-Channel Parameter Handling in Okta Client SDK for Python

published 4h ago modified 4h ago also EUVD-2026-130746

cvss
4.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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.

Patch / fix

  • Okta Okta Client SDK for Python 0.3.1

Is CVE-2026-130153 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
CNA 3.1 4.7 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

Affected products

  • Okta Okta Client SDK for Python

Classification

Weakness
  • CWE-598 Use of HTTP Request With Sensitive Query String
  • CWE-522 Insufficiently Protected Credentials

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.