Okta .NET SDK Abstractions Library API token leak via unvalidated request URLs
Only affects Okta .NET SDK Abstractions Library 1.0.0-beta through 4.0.7 in apps that pass unvalidated external URL inputs to its request routing while using an SSWS API token. Fixed in 4.0.8.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.8
- Who is exposed
- Not reported
Summary
The Okta .NET SDK Abstractions Library does not fully restrict outgoing HTTP requests to the configured Okta organization domain when it processes certain URL formats. An attacker can remotely, without logging in, alter a URL parameter so the library sends the configured SSWS API token to an external host they control.
Written by a model
Original description
In the Okta .NET SDK Abstractions library, outbound HTTP requests are not restricted to the configured Okta organization domain when processing certain URL formats. If a URL parameter is modified to specify an external host, the library may transmit the configured SSWS API token to that unintended destination.
Who should check
Teams running Okta.Sdk.Abstractions 1.0.0-beta through 4.0.7 with an SSWS API token, where the host app passes externally supplied URLs to the library.
“versions 1.0.0-beta through 4.0.7 are affected”
What to do
Upgrade to a fixed version: 4.0.8.
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-130235 (Improper Request URL Validation in the Okta .NET SDK Abstractions Library), 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-130235 (entry last updated 2026-11-19):
Affected:
- Okta Okta .NET SDK Abstractions Library: from 1.0.0, fixed in 4.0.8
Fixed versions: 4.0.8.
Conditions (all must be true for the bug to be hit):
- The host application accepts externally supplied URL inputs and passes them directly to the library's request routing methods without prior validation against a domain allowlist. (source: https://trust.okta.com/security-advisories/improper-request-url-validation-in-the-okta-net-sdk-abstractions-library-cve-2026-130235)
- The SDK client is configured with an SSWS API token. (source: https://trust.okta.com/security-advisories/improper-request-url-validation-in-the-okta-net-sdk-abstractions-library-cve-2026-130235)
- Okta.Sdk.Abstractions versions 1.0.0-beta through 4.0.7. (source: https://trust.okta.com/security-advisories/improper-request-url-validation-in-the-okta-net-sdk-abstractions-library-cve-2026-130235)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130235 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130235 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/improper-request-url-validation-in-the-okta-net-sdk-abstractions-library-cve-2026-130235
- https://github.com/okta/okta-sdk-abstractions-dotnet/releases
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-130235
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-130235"}.Affected versions
- Okta Okta .NET SDK Abstractions LibraryFrom 1.0.0 · fixed in 4.0.8
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 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/improper-request-url-validation-in-the-okta-net-sdk-abstractions-library-cve-2026-130235 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130235 |
| Record | NVD · CVE-2026-130235 |
| Other links 1 | |
| Repository | GitHub · okta/okta-sdk-abstractions-dotnet · Release releases |
Questions about CVE-2026-130235
Is CVE-2026-130235 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
What does this mean?
When an external URL is passed to the library's request routing, the library may send the configured SSWS API token to that unintended destination instead of the Okta service.
Source: trust.okta.com
Which versions are affected by CVE-2026-130235?
Okta .NET SDK Abstractions Library: from 1.0.0 before 4.0.8.
Source: cve.now feed data
Am I affected, and how do I check?
Okta.Sdk.Abstractions versions 1.0.0-beta through 4.0.7 are affected. The setup also requires the host application to accept externally supplied URL inputs and pass them directly to the library's request routing methods without validation against a domain allowlist, and the SDK client to be configured with an SSWS API token. To check the version, look at the Okta.Sdk.Abstractions package reference in your project file or the installed package list.
Source: trust.okta.com
How do I fix CVE-2026-130235?
Upgrade Okta.Sdk.Abstractions to version 4.0.8, which resolves this issue. No vendor patch identifiers are listed for this vulnerability.
Source: trust.okta.com
Related
- CVE-2026-130179Credential Overwriting in Okta .NET SDK Abstractions Library
- CVE-2026-130233Improper Synchronization in the Okta .NET SDK Abstractions Library
- CVE-2026-115547Command Execution via Admin Console Input in Okta Access Gateway
- CVE-2026-130236API Authentication and Rule Generation in the Auth0 Authorization Extension
- 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.