CVE-2022-26135

MEDIUMNVD 6.58.4▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.4 because EPSS predicts 71% probability of exploitation within the next 30 days (top 0.7% of all CVEs). NVD baseline CVSS 6.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
6.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 71%
CISA-KEV: Not listedEPSS: 71%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
8.4(high)
EG Risk
66(Track)
EG Risk 66/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation71% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.3%
KEV
Not listed

Published

June 30, 2022

Last Modified

November 21, 2024

References (6)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:16 UTCEPSS rescore
  2. 2026-07-23 02:09 UTCEG score recompute▲ 1.90
  3. 2026-07-22 22:56 UTCEG score recompute
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-22 14:06 UTCEPSS rescore
  6. 2026-07-20 17:05 UTCEPSS rescore
  7. 2026-07-19 02:27 UTCEPSS rescore
  8. 2026-07-15 16:56 UTCEPSS rescore
  9. 2026-07-15 16:56 UTCEPSS rescore
  10. 2026-07-13 06:11 UTCEPSS rescore
  11. 2026-07-13 06:11 UTCEPSS rescore
  12. 2026-07-12 05:44 UTCEPSS rescore
  13. 2026-07-11 08:25 UTCEPSS rescore
  14. 2026-07-09 19:07 UTCEPSS rescore
  15. 2026-07-07 13:44 UTCEPSS rescore
  16. 2026-07-04 06:29 UTCEPSS rescore
  17. 2026-07-04 06:29 UTCEPSS rescore
  18. 2026-07-01 15:04 UTCEPSS rescore
  19. 2026-06-25 13:48 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-24 14:03 UTCEPSS rescore
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-21 01:58 UTCEPSS rescore
  25. 2026-06-21 01:58 UTCEPSS rescore
Show 32 more
  1. 2026-06-17 17:51 UTCEPSS rescore
  2. 2026-06-17 17:51 UTCEPSS rescore
  3. 2026-06-15 17:46 UTCEPSS rescore
  4. 2026-06-14 23:15 UTCEPSS rescore
  5. 2026-06-14 23:15 UTCEPSS rescore
  6. 2026-06-13 22:58 UTCEPSS rescore
  7. 2026-06-13 22:58 UTCEPSS rescore
  8. 2026-06-12 23:10 UTCEPSS rescore
  9. 2026-06-12 23:10 UTCEPSS rescore
  10. 2026-06-11 13:58 UTCEPSS rescore
  11. 2026-06-11 13:58 UTCEPSS rescore
  12. 2026-06-10 22:16 UTCEPSS rescore
  13. 2026-06-10 13:20 UTCEPSS rescore
  14. 2026-06-07 15:23 UTCEPSS rescore
  15. 2026-06-07 15:23 UTCEPSS rescore
  16. 2026-06-05 22:45 UTCEPSS rescore
  17. 2026-06-04 13:11 UTCEPSS rescore
  18. 2026-06-04 13:11 UTCEPSS rescore
  19. 2026-06-02 20:11 UTCEPSS rescore
  20. 2026-06-02 20:11 UTCEPSS rescore
  21. 2026-06-02 20:11 UTCEPSS rescore
  22. 2026-06-01 13:50 UTCEPSS rescore
  23. 2026-06-01 13:50 UTCEPSS rescore
  24. 2026-06-01 13:50 UTCEPSS rescore
  25. 2026-05-31 00:15 UTCEPSS rescore
  26. 2026-05-31 00:15 UTCEPSS rescore
  27. 2026-05-29 13:42 UTCEPSS rescore
  28. 2026-05-28 13:43 UTCEPSS rescore
  29. 2026-05-28 13:43 UTCEPSS rescore
  30. 2026-05-28 13:43 UTCEPSS rescore
  31. 2026-05-25 19:39 UTCEG score recompute
  32. 2026-05-25 19:39 UTCGHSA enrichment

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCsafe3s/CVE-2022-26135
    First seen Jul 7, 2022

    CVE-2022-26135

    Open source ↗
  • GitHub PoCassetnote/jira-mobile-ssrf-exploit
    First seen Jun 24, 2022

    Exploit code for Jira Mobile Rest Plugin SSRF (CVE-2022-26135)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-26135?
CVE-2022-26135 is a medium vulnerability published on June 30, 2022. 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…
When was CVE-2022-26135 disclosed?
CVE-2022-26135 was first published in the National Vulnerability Database on June 30, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-26135 actively exploited?
CVE-2022-26135 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-26135?
CVE-2022-26135 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.4.
How do I remediate CVE-2022-26135?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-26135, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-26135

Explore →

Is Your Infrastructure Affected by CVE-2022-26135?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs