# CVE-2025-22157: 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 - **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Fix available:** No - **Published:** 20 May 2025 - **Updated:** 26 Feb 2026 - **Also known as:** GHSA-352j-376q-2pmc ## What is CVE-2025-22157? CVE-2025-22157 is a high-severity vulnerability in Atlassian Jira Data Center, published on 20 May 2025. ### Official description 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 Data Center and Server 5.12.0, 10.3.0, 10.4.0, and 10.5.0 of Jira Service Management Data Center and Server This PrivEsc (Privilege Escalation) vulnerability, with a CVSS Score of 7.2, allows an attacker to perform actions as a higher-privileged user. Atlassian recommends that Jira Core Data Center and Server and Jira Service Management Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Jira Core Data Center and Server 9.12: Upgrade to a release greater than or equal to 9.12.20 Jira Service Management Data Center and Server 5.12: Upgrade to a release greater than or equal to 5.12.20 Jira Core Data Center 10.3: Upgrade to a release greater than or equal to 10.3.5 Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.5 Jira Core Data Center 10.4: Upgrade to a release greater than or equal to 10.6.0 Jira Service Management Data Center 10.4: Upgrade to a release greater than or equal to 10.6.0 Jira Core Data Center 10.5: Upgrade to a release greater than or equal to 10.5.1 Jira Service Management Data Center 10.5: Upgrade to a release greater than or equal to 10.5.1 See the release notes. You can download the latest version of Jira Core Data Center and Jira Service Management Data Center from the download center. This vulnerability was reported via our Atlassian (Internal) program. Weakness: CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2025-22157? It affects 2 products. Products: Atlassian Jira Data Center, Atlassian Jira Server. ## How do I fix CVE-2025-22157? No fix has been published for CVE-2025-22157 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-22157 being exploited? There is no known exploitation of CVE-2025-22157 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-2025-22167](https://insights.sbomify.com/CVE-2025-22167/): Path traversal in Jira Software Data Center (high 8.7) - [CVE-2019-20419](https://insights.sbomify.com/CVE-2019-20419/): Other in Jira Server (high 7.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-22157 and fix it if it is affected. What it is: CVE-2025-22157 is a high-severity vulnerability in Atlassian Jira Data Center, published on 20 May 2025. Exploitation: There is no known exploitation of CVE-2025-22157 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-22157/ (Markdown: https://insights.sbomify.com/CVE-2025-22157/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22157 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22157 - OSV: https://osv.dev/vulnerability/CVE-2025-22157 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-22157/ Summaries are generated and may contain mistakes; the official description above is the record.