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

Published Nov 19, 2026
·
Updated

The Okta Client SDK for Python (okta-client-python) includes client authentication values (clientsecret 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.

Affected Software

0 affected components

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade okta-client-python to a version that resolves this vulnerability.

    Fixed in 0.3.1
  2. Operational

    Rotate the client secret for any application that has run the authorization code flow without PAR.

Event History

Nov 19, 2026
CVE Published
via MITRE·09:04 PM
Data Sourced
via MITRE·09:04 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments using the Okta Client SDK for Python authorization code flow are exposed when PAR is disabled, unsupported by the authorization server, or fails and the SDK falls back to standard authorization URL construction.

2

What must occur for sensitive authentication values to be exposed?

A user-agent must make the front-channel authorization request after the SDK constructs the fallback authorization URL. In that path, client_secret values or JWT assertions are included as query parameters.

3

What can be done if an update cannot be applied immediately?

Avoid the fallback path by ensuring Pushed Authorization Requests are enabled and supported by the authorization server, and address PAR failures rather than allowing standard authorization URL construction.

4

How can teams determine whether they may have been affected?

Review authorization-code-flow behavior for cases where PAR was disabled, unsupported, or failed. Check resulting user-agent authorization URLs for client_secret or JWT assertion values in query parameters.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203