# CVE-2022-26135: Server-side request forgery in Jira Core Server

> Remote authenticated users can perform server-side request forgery via a batch endpoint in the Jira Mobile Plugin, allowing full read access to internal resources.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A: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:** 30 Jun 2022
- **Updated:** 29 Oct 2024
- **Also known as:** GHSA-wfhv-4qh5-c632

## What is CVE-2022-26135?

CVE-2022-26135 is a medium-severity server-side request forgery vulnerability in Atlassian Jira Data Center, published on 30 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in Mobile Plugin for Jira Data Center and Server allows a remote, authenticated user (including a user who joined via the sign-up feature) to perform a full read server-side request forgery via a batch endpoint. This affects Atlassian Jira Server and Data Center from version 8.0.0 before version 8.13.22, from version 8.14.0 before 8.20.10, from version 8.21.0 before 8.22.4. This also affects Jira Management Server and Data Center versions from version 4.0.0 before 4.13.22, from version 4.14.0 before 4.20.10 and from version 4.21.0 before 4.22.4.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-26135?

It affects 4 products.


Products: Atlassian Jira Data Center, Atlassian Jira Server, Atlassian Jira Service Desk, Atlassian Jira Service Management.

## How do I fix CVE-2022-26135?

No fix has been published for CVE-2022-26135 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-26135 being exploited?

There is no known exploitation of CVE-2022-26135 in the wild and no public exploit code.

Public exploit code:

- Exploit code for Jira Mobile Rest Plugin SSRF (CVE-2022-26135) (github_poc): https://github.com/assetnote/jira-mobile-ssrf-exploit
-  CVE-2022-26135  (github_poc): https://github.com/safe3s/CVE-2022-26135

## 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-2022-26135 and fix it if it is affected.

What it is: CVE-2022-26135 is a medium-severity server-side request forgery vulnerability in Atlassian Jira Data Center, published on 30 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-26135 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-2022-26135/ (Markdown: https://insights.sbomify.com/CVE-2022-26135/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-26135
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-26135
- OSV: https://osv.dev/vulnerability/CVE-2022-26135

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-26135/
Summaries are generated and may contain mistakes; the official description above is the record.