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

Published: 2022-06-30 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-26135 is rated Moderate Risk (55.8/100): CVSS Medium severity, with high exploitation likelihood (EPSS 84.00%, 99th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-26135

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-10 89.29% 84.00% -5.28%
2 2026-03-04 83.06% 89.29% +6.23%
3 2026-03-01 — 83.06% —

Full EPSS history (46 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-26135

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0
4.0 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.0 2.9 [email protected]

Weakness enumeration for CVE-2022-26135

Affected software / configurations for CVE-2022-26135

Vendor Product Version Raw CPE
atlassian jira_data_center >= 8.0.0, < 8.13.22 cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*
atlassian jira_data_center >= 8.14.0, < 8.20.10 cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*
atlassian jira_data_center >= 8.21.0, < 8.22.4 cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*
atlassian jira_server >= 8.0.0, < 8.13.22 cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*
atlassian jira_server >= 8.14.0, < 8.20.10 cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*
atlassian jira_server >= 8.21.0, < 8.22.4 cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*
atlassian jira_service_desk >= 4.0.0, < 4.13.22 cpe:2.3:a:atlassian:jira_service_desk:*:*:*:*:data_center:*:*:*
atlassian jira_service_desk >= 4.0.0, < 4.13.22 cpe:2.3:a:atlassian:jira_service_desk:*:*:*:*:server:*:*:*
atlassian jira_service_management >= 4.14.0, < 4.20.10 cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:data_center:*:*:*
atlassian jira_service_management >= 4.14.0, < 4.20.10 cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:server:*:*:*
atlassian jira_service_management >= 4.21.0, < 4.22.4 cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:data_center:*:*:*
atlassian jira_service_management >= 4.21.0, < 4.22.4 cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:server:*:*:*

References for CVE-2022-26135

cvelogic Threat Intelligence