GHSA-qhr6-6cgv-6638
MEDIUMImproper Memory Cleanup in the Okta Java SDK
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
com.okta.sdk:okta-sdk-rootReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Description
In the Okta Java SDK, specific multithreaded implementations may encounter memory issues as threads are not properly cleaned up after requests are completed. Over time, this can degrade performance and availability in long-running applications and may result in a denial-of-service condition under sustained load.
Affected product and versions
You may be affected by this vulnerability if you meet the following preconditions:
- Using the Okta Java SDK between versions 21.0.0 and 24.0.0, and
- Implementing a long-running application using the ApiClient in a multi-threaded manner.
Resolution
Upgrade Okta/okta-sdk-java to versions 24.0.1 or greater.
Acknowledgement
Okta would like to thank Andrew Pikler (pyckle) for their discovery and responsible disclosure.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.okta.sdk:okta-sdk-root | ≥ 21.0.0&&< 24.0.1 | 24.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.okta.sdk:okta-sdk-root. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.okta.sdk:okta-sdk-root to 24.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qhr6-6cgv-6638 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qhr6-6cgv-6638 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-qhr6-6cgv-6638. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-qhr6-6cgv-6638 in your dependencies?
O3 detects GHSA-qhr6-6cgv-6638 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.