Okta Swift Management SDK path traversal via unencoded path parameters
Affects Okta Swift Management SDK before 0.1.1 when an application passes unencoded path traversal input to an SDK path parameter and the client uses session-level credentials. Fixed in 0.1.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.1.1
- Who is exposed
- Specific setups only
Summary
Written by a model
The Okta Swift Management SDK does not percent-encode forward slash (/) characters during path parameter interpolation. If an application supplies input containing relative path sequences (e.g., ../) to an SDK method, standard URL normalization may direct the outbound request to an alternative Okta Management API endpoint.
Who should check
Teams using the Okta Swift Management SDK before 0.1.1 that pass untrusted input into SDK path parameters
“Customers using the Okta Swift Management SDK versions prior to 0.1.1 are affected.”
What to do
Check whether your setup matches what the bug needs.
An application passes input containing unencoded path traversal sequences to an SDK path parameter. The SDK client is configured with session-level authentication credentials.Upgrade to a fixed version: 0.1.1.
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-130234 (Path Parameter Encoding in Okta Swift Management SDK), 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-130234 (entry last updated 2026-11-19):
Affected:
- Okta Okta Swift Management SDK: fixed in 0.1.1
Fixed versions: 0.1.1.
Conditions (all must be true for the bug to be hit):
- An application passes input containing unencoded path traversal sequences to an SDK path parameter. (source: https://trust.okta.com/security-advisories/path-parameter-encoding-in-okta-swift-management-sdk-cve-2026-130234)
- The SDK client is configured with session-level authentication credentials. (source: https://trust.okta.com/security-advisories/path-parameter-encoding-in-okta-swift-management-sdk-cve-2026-130234)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-130234 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130234 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/path-parameter-encoding-in-okta-swift-management-sdk-cve-2026-130234
- https://github.com/okta/okta-sdk-swift/tags
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-130234
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-130234"}.Affected versions
- Okta Okta Swift Management SDKfixed in 0.1.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8/10CVSS 8.0
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
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/path-parameter-encoding-in-okta-swift-management-sdk-cve-2026-130234 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130234 |
| Record | NVD · CVE-2026-130234 |
| Other links 1 | |
| Repository | GitHub · okta/okta-sdk-swift · tags |
Questions about CVE-2026-130234
Is CVE-2026-130234 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?
Input containing unencoded path traversal sequences such as ../ that is passed to an SDK path parameter can, after standard URL normalization, direct the SDK's outbound request to an alternative Okta Management API endpoint.
Source: trust.okta.com
Which versions are affected by CVE-2026-130234?
Okta Swift Management SDK: before 0.1.1.
Source: cve.now feed data
Am I affected, and how do I check?
Versions of the Okta Swift Management SDK before 0.1.1 are in the affected range. Check the SDK version pinned in the project's dependency configuration. The setup also matters: the application must pass unencoded path traversal input to a path parameter, and the SDK client must be configured with session-level authentication credentials.
Source: trust.okta.com
How do I fix CVE-2026-130234?
Upgrade the Okta Swift Management SDK to version 0.1.1, the fixed version named in the advisory.
Source: trust.okta.com
Related
- CVE-2026-115547Command Execution via Admin Console Input in Okta Access Gateway
- CVE-2026-130235Improper Request URL Validation in the Okta .NET SDK Abstractions Library
- CVE-2026-130236API Authentication and Rule Generation in the Auth0 Authorization Extension
- CVE-2026-130179Credential Overwriting in Okta .NET SDK Abstractions Library
- 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.