{"answers":{"affected":"2 open source packages ship an affected version, including com.okta.sdk:okta-sdk-root. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-67505 in the wild and no public exploit code.","fix":"Upgrade com.okta.sdk:okta-sdk-root to 20.0.1 or later.","what":"CVE-2025-67505 is a high-severity 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."},"fix_prompt":"Check this codebase for CVE-2025-67505 and fix it if it is affected.\n\nWhat it is: CVE-2025-67505 is a high-severity 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.\nExploitation: There is no known exploitation of CVE-2025-67505 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.okta.sdk:okta-sdk-root (Maven): affected from 11.0.0; fixed in 20.0.1\n- com.okta.sdk:okta-sdk-root (Maven): affected from 11.0.0; fixed in 20.0.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-67505/ (Markdown: https://insights.sbomify.com/CVE-2025-67505/index.md)","id":"CVE-2025-67505","markdown":"https://insights.sbomify.com/CVE-2025-67505/index.md","name":"CVE-2025-67505","record":{"aliases":["GHSA-j5gq-897m-2rff"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Okta Java SDK","requires_auth":"low_privilege","summary":"Concurrent API requests in the Okta Java SDK may mix response data, potentially exposing or altering information across different user sessions.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"java_management_sdk","vendor":"okta"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"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 to influence another request’s response. This issue is fixed in version 20.0.1.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Race condition in the Okta Java SDK","id":"CVE-2025-67505","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"PipesHub Vulnerable to Path Traversal through Unauthenticated Arbitrary File Upload","id":"CVE-2025-67506"},"packages":[{"ecosystem":"Maven","fixed":["20.0.1"],"introduced":["11.0.0"],"last_affected":[],"package":"com.okta.sdk:okta-sdk-root","purl":null,"source":"GHSA-j5gq-897m-2rff"},{"ecosystem":"Maven","fixed":["20.0.1"],"introduced":["11.0.0"],"last_affected":[],"package":"com.okta.sdk:okta-sdk-root","purl":"pkg:maven/com.okta.sdk/okta-sdk-root","source":"GHSA-j5gq-897m-2rff"}],"prev":{"headline":"WBCE CMS has Weak Random Number Generator in Password Generation Function","id":"CVE-2025-67504"},"products":["okta-sdk-java"],"published":"2025-12-10","related":[{"cvss_score":5.3,"headline":"Improper Memory Cleanup in the Okta Java SDK","id":"CVE-2025-66033","kev_date_added":null,"published":"2025-12-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-11","vendors":["okta"]},"summary":"Concurrent API requests in the Okta Java SDK may mix response data, potentially exposing or altering information across different user sessions.","url":"https://insights.sbomify.com/CVE-2025-67505/"}