Jira Data CenterApplication · Atlassian
CVE-2025-22167
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThis 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in Jira Software Data Center and Server versions 9.12.0 through 11.0.0 allows an authenticated attacker to write arbitrary files to any filesystem location writable by the Jira JVM process, potentially enabling remote code execution or complete system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Jira Data CenterApplication
>= 9.12.0, < 9.12.28>= 10.3.0, < 10.3.12>= 11.0.0, < 11.1.0
Jira ServerApplication
>= 9.12.0, < 9.12.28>= 10.3.0, < 10.3.12>= 11.0.0, < 11.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Jira versionCheck the Jira application version by navigating to Jira Administration > System > Troubleshooting and support tools, or by inspecting the 'atlassian-jira/WEB-INF/classes/com/atlassian/jira/version.properties' file in the Jira home directory.Affected if The installed version falls within 9.12.0 to 9.12.27, 10.3.0 to 10.3.11, or 11.0.0.
-
Verify Jira user authentication settingsReview Jira user management settings to confirm which users have access to Jira. The vulnerability requires an authenticated user, so check if any internal or directory users exist beyond administrators.Affected if There are authenticated users with any level of access who could potentially trigger the vulnerable file write functionality.
-
Review Jira process filesystem permissionsExamine the operating system permissions for the user account running the Jira JVM process. Check what directories that user account has write access to beyond the intended Jira data directories.Affected if The Jira process user has write access to directories outside the designated Jira home and install directories.
-
Inspect Jira access logs for path traversal patternsReview Jira access logs (typically in /logs/atlassian-jira-access-log.xml or similar) for requests containing patterns like '../' or absolute file paths in parameters that might indicate exploitation attempts.Affected if Log entries show suspicious requests with directory traversal sequences or unusual file path parameters.
You are affected if your Jira version is 9.12.0-9.12.27, 10.3.0-10.3.11, or 11.0.0 AND authenticated users exist AND the Jira process has broad filesystem write permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.12.2810.3.1211.1.0
Upgrade Jira to version 9.12.28 or higher, 10.3.12 or higher, or 11.1.0 or higher per Atlassian's advisory.
Jira 9.12.28+, 10.3.12+, or 11.1.0+ (depending on your current major version branch)
- 1. Back up your Jira Data Center/Server instance including database and attachments directory
- 2. Review Jira release notes for the target version to understand changes
- 3. Download the appropriate fixed version (9.12.28+, 10.3.12+, or 11.1.0+) from the Atlassian download center
- 4. Stop the Jira application
- 5. Run the upgrade installer following Atlassian's standard upgrade documentation
- 6. Verify the upgrade was successful and Jira starts normally
- 7. Test that normal Jira functionality works as expected
- 8. Validate the path traversal vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jira Data Center
Scoped from the published advisory
- Consultation1.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22167 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22167 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data