Security Resilience

CVE-2025-67505

Race Condition in Okta Java Management Sdk 11.0.0 – 20.0.1

Published
10 December 2025
Modified
25 September 2026
Patch / advisory
CVSS Score v3.1 8.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
EPSS Score 0.0021 10th percentile
Risk Priority 57 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-67505 is a high-severity Race Condition (CWE-362) vulnerability in Okta Java Management Sdk. Its CVSS base score is 8.4 (High).

Operationally, ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-39 (Process Isolation) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response…

more

to influence another request’s response. This issue is fixed in version 20.0.1.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-66033Same product: Okta Java Management Sdk
CVE-2026-78623Same product class: directory / identity
CVE-2024-9191Same product class: directory / identity
CVE-2026-78574Same product class: directory / identity
CVE-2023-0093Same product class: directory / identity
CVE-2023-0392Same product class: directory / identity
CVE-2024-7061Same product class: directory / identity
CVE-2026-78627Same product class: directory / identity
CVE-2026-69851Same product class: directory / identity
CVE-2023-5003Same product class: directory / identity

Affected Assets

okta
java management sdk
11.0.0 — 20.0.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Maintaining separate execution domains for each process structurally eliminates unintended concurrent access to the same shared resources.

Preventing unintended information transfer through shared system resources directly addresses the improper concurrent modification that defines a race condition.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect race conditions, but does not prevent them at design or coding time.

prevents

Secure coding standards explicitly forbid unsafe concurrent access patterns and mandate atomic operations or locks.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-362, a class-level weakness, and none of its children carries one either.

References