CVE-2025-66033: Improper Memory Cleanup in the Okta Java SDK
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.
Other sources
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.
— NVD
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-66033?
CVE-2025-66033 has a moderate severity level due to potential memory issues affecting performance and availability.
How do I fix CVE-2025-66033?
To fix CVE-2025-66033, upgrade the Okta Java SDK to a version higher than 24.0.1.
What systems are affected by CVE-2025-66033?
CVE-2025-66033 affects the Okta Java SDK versions from 21.0.0 to 24.0.0.
What problems can CVE-2025-66033 cause?
CVE-2025-66033 can lead to memory issues that degrade the performance and availability of long-running applications.
Is there a workaround for CVE-2025-66033?
Currently, there are no documented workarounds for CVE-2025-66033 other than upgrading the SDK.