Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Path Traversal Arbitrary File Write in Atlassian Jira Software Data Center and Server

IdentifiersCVE-2025-22167CWE-22· Improper Limitation of a Pathname…

CVE-2025-22167 is a high-severity path traversal vulnerability in Atlassian Jira Software Data Center and Server. According to the provided content, the issue was introduced in versions 9.12.0, 10.3.0, and remains present in 11.0.0. Successful exploitation allows an attacker to modify any filesystem path writable by the Jira JVM process, making this effectively an arbitrary file write condition via path traversal. The provided material does not identify the specific vulnerable endpoint, function, or code path.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can write or modify files at arbitrary paths that are writable by the Jira JVM process. Depending on the Jira deployment, filesystem permissions, and reachable writable locations, this can lead to application tampering, configuration manipulation, data corruption, persistence, denial of service, or potentially further compromise if written files are later interpreted or executed by the application or host environment.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce risk by limiting access to Jira to trusted users and networks, restricting exposure of administrative and sensitive application functionality, and ensuring the Jira JVM process runs with the minimum filesystem privileges necessary. Constrain write permissions on the host so the Jira process cannot modify sensitive system, application, or web-accessible paths. Monitor for unexpected file creation or modification by the Jira process. The provided content does not include any vendor-specified temporary workaround beyond upgrading.

Remediation

Patch, then assume compromise.

Atlassian recommends upgrading Jira Software Data Center and Server to a fixed release. The provided fixed versions are: Jira 9.12.x to 9.12.28 or later, Jira 10.3.x to 10.3.12 or later, and Jira 11.0.x to 11.1.0 or later. If possible, upgrade to the latest available version from Atlassian.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AtlassianJira Data Centerapplication
AtlassianJira Serverapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.