Skip to main content

CVE-2026-21601Atlassian Jira Service Management Data Center vulnerability

Schedule itHigh8.7EPSS not scored yet

CVE-2026-21601 is a vulnerability in Atlassian Jira Service Management Data Center, rated high (8.7 on CVSS 4.0).

Why this priority: High severity, with no exploitation signal yet.

Published · Updated · NVD status: Received

What it is

The record does not classify the weakness yet; the description below says what the reporter found.

How it is reached

An attacker can exploit it over the network, without an account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade Atlassian Jira Service Management Data Center to a fixed version for your release line (11.3.13, 10.3.27).
  2. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.

Description from NVD

This High severity BASM (Broken Authentication & Session Management) vulnerability was introduced in versions 10.0.0 and 11.0.0 of Jira Service Management Data Center.

This BASM (Broken Authentication & Session Management) vulnerability, with a CVSS Score of 8.7, allows an unauthenticated attacker to perform actions as another user.

Atlassian recommends that Jira Service Management Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:

* Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27

* Jira Service Management Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13

See the release notes (https://confluence.atlassian.com/servicemanagement/jira-service-management-release-notes-780083086.html). You can download the latest version of Jira Service Management Data Center from the download center (https://www.atlassian.com/software/jira/service-management/download-archives).

This vulnerability was discovered by Nagli and reported via our Bug Bounty program

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Atlassian Jira Service Management Data Center. Start from where it runs and what it is connected to.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.

Questions to answer about your own systems

  • Where does Atlassian Jira Service Management Data Center run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.