Skip to content

Improper Memory Cleanup in the Okta Java SDK

Moderate severity GitHub Reviewed Published Dec 10, 2025 in okta/okta-sdk-java • Updated Dec 11, 2025

Package

mavencom.okta.sdk:okta-sdk-root (Maven)

Affected versions

>= 21.0.0, <= 24.0.0

Patched versions

24.0.1

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.

References

@femiajiboye-oktafemiajiboye-okta published to okta/okta-sdk-java Dec 10, 2025
Published to the GitHub Advisory Database Dec 10, 2025
Reviewed Dec 10, 2025
Published by the National Vulnerability DatabaseDec 10, 2025
Last updated Dec 11, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector:More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity:More severe for the least complex attacks.
Privileges required:More severe if no privileges are required.
User interaction:More severe when no user interaction is required.
Scope:More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality:More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity:More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability:More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(12th percentile)

Weaknesses

Missing Release of Memory after Effective Lifetime

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. Learn more on MITRE.

CVE ID

CVE-2025-66033

GHSA ID

GHSA-qhr6-6cgv-6638

Source code

Credits

LoadingChecking history
See something to contribute? Suggest improvements for this vulnerability.