Access-control errors via unsynchronized concurrent responses
Published Dec 10, 2025 · Updated Dec 11, 2025
Race condition in Okta Java SDK 11.0.0 through 20.0.0 allows remote authenticated users to misapply response status and headers. ApiClient.invokeAPI handles concurrent calls without synchronization, so one response's status code or headers can be read as another response's metadata. Exploitation requires a multithreaded application that uses ApiClient response status in access-control flows, where the mix-up can produce incorrect authorization decisions.
Summary
What happened
Race condition in Okta Java SDK 11.0.0 through 20.0.0 allows remote authenticated users to misapply response status and headers. ApiClient.invokeAPI handles concurrent calls without synchronization, so one response's status code or headers can be read as another response's metadata. Exploitation requires a multithreaded application that uses ApiClient response status in access-control flows, where the mix-up can produce incorrect authorization decisions.
The record
- CVE
- CVE-2025-67505
- Published
- Dec 10, 2025
- Updated
- Dec 11, 2025
- Vendor
- Okta
- Product
- Okta Java SDK
- Classifications
- CWE-362
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 10, 2025CVE publishedPublication date reported by the CVE source.
- Dec 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 11.0.0, < 20.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo