CVE-2026-130153Okta Client SDK for Python insufficiently protected credentials
CVE-2026-130153 is a insufficiently protected credentials in Okta Client SDK for Python, rated medium (4.7 on CVSS 3.1).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
Credentials are stored or sent in a way others can recover.
How it is reached
An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker sign in with credentials the vendor shipped or stored unprotected. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade Okta Client SDK for Python to 0.3.1 or later.
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
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 this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Credentials kept in code, configuration, images or firmware. The flaw sits between a stored secret and anyone who can read where it is kept.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between a stored secret and anyone who can read where it is kept. An attacker who crosses it can sign in with credentials the vendor shipped or stored unprotected.
Questions to answer about your own systems
- Where does Okta Client SDK for Python run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
14-day free trial
Understand how your systems connect.
See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.