Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

  1. ID reserved

    By atlassian

  2. · 4 months later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-26135, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium6.5CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVDNVD · Modified3.1Medium6.5CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
71.6% · top 0.6% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.5.

Affected products

  • Atlassian · Jira Core Server

    • affected 8.0.0 – < unspecified
    • affected unspecified – < 8.13.22
    • affected 8.14.0 – < unspecified
    • affected unspecified – < 8.20.10
    • affected 8.21.0 – < unspecified
    • affected unspecified – < 8.22.4
  • Atlassian · Jira Software Server

    • affected 8.0.0 – < unspecified
    • affected unspecified – < 8.13.22
    • affected 8.14.0 – < unspecified
    • affected unspecified – < 8.20.10
    • affected 8.21.0 – < unspecified
    • affected unspecified – < 8.22.4
  • Atlassian · Jira Software Data Center

    • affected 8.0.0 – < unspecified
    • affected unspecified – < 8.13.22
    • affected 8.14.0 – < unspecified
    • affected unspecified – < 8.20.10
    • affected 8.21.0 – < unspecified
    • affected unspecified – < 8.22.4
  • Atlassian · Jira Service Management Server

    • affected 4.0.0 – < unspecified
    • affected unspecified – < 4.13.22
    • affected 4.14.0 – < unspecified
    • affected unspecified – < 4.20.10
    • affected 4.21.0 – < unspecified
    • affected unspecified – < 4.22.4
  • Atlassian · Jira Service Management Data Center

    • affected 4.0.0 – < unspecified
    • affected unspecified – < 4.13.22
    • affected 4.14.0 – < unspecified
    • affected unspecified – < 4.20.10
    • affected 4.21.0 – < unspecified
    • affected unspecified – < 4.22.4

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-26135 badge
[![CVE-2022-26135](https://cveledger.app/badge/CVE-2022-26135.svg)](https://cveledger.app/cve/CVE-2022-26135)

Record last updated .