CVE-2022-26135
A public proof of concept exists; no exploitation attested.
- Published2022-06-30
- Fixed in8.22.4 · 8.20.10 · 8.13.22
- WeaknessCWE-918
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2022-06-3006:15CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-26135?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-26135?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.x | ≥ 8.21.0, < 8.22.4 | 8.22.4 | NVD |
| 8.x | ≥ 8.14.0, < 8.20.10 | 8.20.10 | NVD |
| 8.x | ≥ 8.0.0, < 8.13.22 | 8.13.22 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.x | ≥ 8.21.0, < 8.22.4 | 8.22.4 | NVD |
| 8.x | ≥ 8.14.0, < 8.20.10 | 8.20.10 | NVD |
| 8.x | ≥ 8.0.0, < 8.13.22 | 8.13.22 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.x | ≥ 4.21.0, < 4.22.4 | 4.22.4 | NVD |
| 4.x | ≥ 4.14.0, < 4.20.10 | 4.20.10 | NVD |
1 more product in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Atlassian Jira to 8.22.4 · 8.20.10 · 8.13.22
Advisories and patches
- confluence.atlassian.comMitigation · Vendor Advisory
- jira.atlassian.comVendor Advisory
- jira.atlassian.comVendor Advisory
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 2 repositories, unverifiedassetnote/jira-mobile-ssrf-exploitsafe3s/CVE-2022-26135 PoC-in-GitHub
Sources
- CISA-ADPSSVC decisionnone2024-10-03
- OpenCVESSVC decisionnone—
- CISA-ADPCVSS 3.16.52024-10-03
- NVDCVSS 3.16.5read 2026-10-23
- NVDCVSS 2.04read 2026-10-23
- CISA-ADPweakness (CWE)CWE-9182024-10-03
- NVDweakness (CWE)CWE-918read 2026-10-23
- FIRST EPSSEPSS score71.6 %read 2026-10-23
- PoC-in-GitHubproof of concept2read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Published
- 2022-06-30
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2022-26135?
Is CVE-2022-26135 actively exploited?
What is the CVSS score for CVE-2022-26135?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.