# CVE-2025-22167: Path traversal in Jira Software Data Center > An attacker can modify any filesystem path writable by the Jira JVM process, requiring an upgrade to a patched version. - **Severity:** High 8.7 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 22 Oct 2025 - **Updated:** 26 Feb 2026 - **Also known as:** GHSA-wvj6-fjwf-f68m ## What is CVE-2025-22167? 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. ### Official 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: Jira Software Data Center and Server 9.12: Upgrade to a release greater than or equal to 9.12.28 Jira Software Data Center and Server 10.3: Upgrade to a release greater than or equal to 10.3.12 Jira Software Data Center and Server 11.0: Upgrade to a release greater than or equal to 11.1.0 See 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2025-22167? It affects 2 products. Products: Atlassian Jira Data Center, Atlassian Jira Server. ## How do I fix CVE-2025-22167? No fix has been published for CVE-2025-22167 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-22167 being exploited? There is no known exploitation of CVE-2025-22167 in the wild and no public exploit code. ## Other vulnerabilities in Atlassian Jira Data Center - [CVE-2021-26086](https://insights.sbomify.com/CVE-2021-26086/): Atlassian Jira Server and Data Center Path Traversal (medium 5.3, exploited in the wild) - [CVE-2022-0540](https://insights.sbomify.com/CVE-2022-0540/): Auth bypass in Jira Core Server (critical 9.8) - [CVE-2020-36239](https://insights.sbomify.com/CVE-2020-36239/): Deserialization in Jira Core Data Center (critical 9.8) - [CVE-2019-20419](https://insights.sbomify.com/CVE-2019-20419/): Other in Jira Server (high 7.8) - [CVE-2024-21685](https://insights.sbomify.com/CVE-2024-21685/): Information disclosure in Jira Core Data Center (high 7.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-22167 and fix it if it is affected. What 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. Exploitation: There is no known exploitation of CVE-2025-22167 in the wild and no public exploit code. Affected product: Atlassian Jira Data Center. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-22167/ (Markdown: https://insights.sbomify.com/CVE-2025-22167/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22167 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22167 - OSV: https://osv.dev/vulnerability/CVE-2025-22167 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-22167/ Summaries are generated and may contain mistakes; the official description above is the record.