dbcve.org
Jira Data CenterApplication · Atlassian

CVE-2022-26135

MEDIUM · 6.5 CVSS v3.1 Published 2022-06-30
Fix available
A fix is available. Upgrade to 4.13.22 / 4.20.10 or later.
See remediation →
71/100
Remediation priority · Elevated
High EPSS Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A server-side request forgery (SSRF) vulnerability in the Mobile Plugin for Jira allows authenticated users, including self-registered users, to make the Jira server fetch arbitrary URLs and read the responses via a batch endpoint. This enables internal network reconnaissance and potential access to internal services.

MitigationUpdate Jira Server and Data Center to version 8.13.22, 8.20.10, 8.22.4 or later (or corresponding 4.x versions for Jira Management) to patch the vulnerable Mobile Plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jira Data CenterApplication
Affected:>= 8.0.0, < 8.13.22>= 8.14.0, < 8.20.10>= 8.21.0, < 8.22.4
Jira ServerApplication
Affected:>= 8.0.0, < 8.13.22>= 8.14.0, < 8.20.10>= 8.21.0, < 8.22.4
Jira Service DeskApplication
Affected:>= 4.0.0, < 4.13.22
Jira Service ManagementApplication
Affected:>= 4.14.0, < 4.20.10>= 4.21.0, < 4.22.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jira version
    Check the installed Jira version via the Atlassian marketplace or the /rest/api/2/serverInfo endpoint. Compare against affected ranges: 8.0.0 to 8.13.21, 8.14.0 to 8.20.9, 8.21.0 to 8.22.3 for Jira Server/Data Center; or 4.0.0 to 4.13.21, 4.14.0 to 4.20.9, 4.21.0 to 4.22.3 for Jira Service Management/Service Desk.
    Affected if Installed version falls within any of the listed vulnerable ranges.
  2. Confirm Mobile Plugin is present
    Navigate to Jira administration, then to Apps > Manage apps. Look for 'Jira Mobile' or 'Mobile Plugin' in the list of installed add-ons.
    Affected if The Mobile Plugin add-on is listed as installed.
  3. Verify Mobile Plugin is enabled
    In Manage apps, check the status of the Mobile Plugin. It should show as 'Enabled' for the vulnerability to be exploitable.
    Affected if Mobile Plugin is in the enabled state.
  4. Check user registration settings
    In Jira administration under Security > Signup and directory, verify whether 'Allow users to sign up' or self-registration is enabled.
    Affected if Self-registration is permitted, allowing external attackers to obtain authenticated access.
  5. Inspect for the vulnerable batch endpoint
    Review HTTP access logs for requests to /rest/mobile/1.0/batch or similar Mobile Plugin endpoints. These endpoints handle batched API calls and are the vector for the SSRF.
    Affected if Unusual or unauthorized requests to Mobile Plugin batch endpoints are present in logs.

You are affected if your Jira version is within the vulnerable ranges AND the Mobile Plugin is enabled and accessible to authenticated users, including self-registered accounts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.13.22 / 4.20.10 / 4.22.4 or later
Fixed in 4.13.224.20.104.22.4
Interim mitigation

Update Jira Server and Data Center to version 8.13.22, 8.20.10, 8.22.4 or later (or corresponding 4.x versions for Jira Management) to patch the vulnerable Mobile Plugin.

Recommended fix High confidence

Upgrade to Jira 8.13.22, 8.20.10, or 8.22.4 (for 8.x) or Jira Service Management 4.13.22, 4.20.10, or 4.22.4 (for 4.x)

  1. 1. Identify your current Jira version by navigating to Jira Administration > System > System Info (or /secure/admin/ViewSystemInfo.jspa)
  2. 2. Determine which upgrade path applies based on your current version: if < 8.13.22 upgrade to 8.13.22; if >= 8.13.22 and < 8.20.10 upgrade to 8.20.10; if >= 8.20.10 and < 8.22.4 upgrade to 8.22.4
  3. 3. For Jira Service Management/Service Desk: if < 4.13.22 upgrade to 4.13.22; if >= 4.13.22 and < 4.20.10 upgrade to 4.20.10; if >= 4.20.10 and < 4.22.4 upgrade to 4.22.4
  4. 4. Review Atlassian's upgrade documentation and release notes for your target version to understand prerequisites
  5. 5. Perform a full backup of your Jira database and configuration before upgrading
  6. 6. Test the upgrade in a staging environment that mirrors production
  7. 7. Apply the upgrade during a planned maintenance window following Atlassian's installation guide
  8. 8. Verify the upgrade was successful by checking the version in System Info
Caveat Review Atlassian's release notes for breaking changes between your current version and target version, particularly around database migrations and plugin compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jira Data Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26135 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data