# CVE-2025-66033: Improper Memory Cleanup in the Okta Java SDK > Improper memory cleanup in the Okta Java SDK can cause resource exhaustion and denial of service in long-running multithreaded applications. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Dec 2025 - **Updated:** 11 Dec 2025 - **Also known as:** GHSA-qhr6-6cgv-6638 ## What is CVE-2025-66033? CVE-2025-66033 is a medium-severity denial of service vulnerability in okta-sdk-java, published on 10 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Okta Java Management SDK facilitates interactions with the Okta management API. In versions 21.0.0 through 24.0.0, 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. In addition to using the affected versions, users may be at risk if they are implementing a long-running application using the ApiClient in a multi-threaded manner. This issue is fixed in version 24.0.1. Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime) ## Which versions are affected by CVE-2025-66033? 2 open source packages ship an affected version, including com.okta.sdk:okta-sdk-root. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.okta.sdk:okta-sdk-root` | Maven | From 21.0.0 | 24.0.1 | | `com.okta.sdk:okta-sdk-root` | Maven | From 21.0.0 | 24.0.1 | Products: Okta Java Management Sdk. ## How do I fix CVE-2025-66033? Upgrade com.okta.sdk:okta-sdk-root to 24.0.1 or later. ## Is CVE-2025-66033 being exploited? There is no known exploitation of CVE-2025-66033 in the wild and no public exploit code. ## Other vulnerabilities in okta-sdk-java - [CVE-2025-67505](https://insights.sbomify.com/CVE-2025-67505/): Race condition in the Okta Java SDK (high 8.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-66033 and fix it if it is affected. What it is: CVE-2025-66033 is a medium-severity denial of service vulnerability in okta-sdk-java, published on 10 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-66033 in the wild and no public exploit code. Affected packages and fixed versions: - com.okta.sdk:okta-sdk-root (Maven): affected from 21.0.0; fixed in 24.0.1 - com.okta.sdk:okta-sdk-root (Maven): affected from 21.0.0; fixed in 24.0.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-66033/ (Markdown: https://insights.sbomify.com/CVE-2025-66033/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-66033 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-66033 - OSV: https://osv.dev/vulnerability/CVE-2025-66033 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-66033/ Summaries are generated and may contain mistakes; the official description above is the record.