{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-22167 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-22167 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-22167 is a high-severity path traversal vulnerability in Atlassian Jira Data Center, published on 22 Oct 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-22167 and fix it if it is affected.\n\nWhat it is: CVE-2025-22167 is a high-severity path traversal vulnerability in Atlassian Jira Data Center, published on 22 Oct 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-22167 in the wild and no public exploit code.\n\nAffected product: Atlassian Jira Data Center. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-22167/ (Markdown: https://insights.sbomify.com/CVE-2025-22167/index.md)","id":"CVE-2025-22167","markdown":"https://insights.sbomify.com/CVE-2025-22167/index.md","name":"CVE-2025-22167","record":{"aliases":["GHSA-wvj6-fjwf-f68m"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira Software","requires_auth":"low_privilege","summary":"An attacker can modify any filesystem path writable by the Jira JVM process, requiring an upgrade to a patched version.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_data_center","vendor":"atlassian"},{"product":"jira_server","vendor":"atlassian"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"This High severity Path Traversal (Arbitrary Write) vulnerability was introduced in versions: 9.12.0, 10.3.0 and remain present in 11.0.0 of Jira Software Data Center and Server. This Path Traversal (Arbitrary Write) vulnerability, with a CVSS Score of 8.7, allows an attacker to modify any filesystem path writable by the Jira JVM process. Atlassian recommends that Jira Software Data Center and Server customers upgrade to the latest version; if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:\r\n Jira Software Data Center and Server 9.12: Upgrade to a release greater than or equal to 9.12.28\r\n Jira Software Data Center and Server 10.3: Upgrade to a release greater than or equal to 10.3.12\r\n Jira Software Data Center and Server 11.0: Upgrade to a release greater than or equal to 11.1.0\r\n\r\nSee the release notes. You can download the latest version of Jira Software Data Center and Server from the download center. This vulnerability was reported via our Atlassian (Internal) program.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Path traversal in Jira Software Data Center","id":"CVE-2025-22167","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira_data_center","products":["atlassian:jira_data_center","atlassian:jira_server"],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in Jira Align","id":"CVE-2025-22168"},"packages":[],"prev":{"headline":"Denial of service in Confluence Data Center","id":"CVE-2025-22166"},"products":["Jira Software Data Center","Jira Software Server"],"published":"2025-10-22","related":[{"cvss_score":5.3,"headline":"Atlassian Jira Server and Data Center Path Traversal","id":"CVE-2021-26086","kev_date_added":"2024-11-12","published":"2021-08-16"},{"cvss_score":9.8,"headline":"Auth bypass in Jira Core Server","id":"CVE-2022-0540","kev_date_added":null,"published":"2022-04-20"},{"cvss_score":9.8,"headline":"Deserialization in Jira Core Data Center","id":"CVE-2020-36239","kev_date_added":null,"published":"2021-07-29"},{"cvss_score":7.8,"headline":"Other in Jira Server","id":"CVE-2019-20419","kev_date_added":null,"published":"2020-07-03"},{"cvss_score":7.4,"headline":"Information disclosure in Jira Core Data Center","id":"CVE-2024-21685","kev_date_added":null,"published":"2024-06-18"},{"cvss_score":7.2,"headline":"This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions: 9.12.0, 10.3.0, 10.4.0, and 10.5.0 of Jira Core","id":"CVE-2025-22157","kev_date_added":null,"published":"2025-05-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-02-26","vendors":["Atlassian"]},"summary":"An attacker can modify any filesystem path writable by the Jira JVM process, requiring an upgrade to a patched version.","url":"https://insights.sbomify.com/CVE-2025-22167/"}