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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
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
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 | 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 include Okta Java Management Sdk.
How do I fix CVE-2025-66033?
Upgrade com.okta.sdk:okta-sdk-root to 24.0.1 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
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
Sources
Also known as GHSA-qhr6-6cgv-6638.