Loading story…
Atlassian disclosed CVE-2019-14994, a critical path traversal flaw in Jira Service Desk Server and Data Center that lets an authenticated user with customer portal access bypass portal restrictions and view issues across Jira Service Desk, Jira Core, and Jira Software projects on the same instance. The bug affected multiple releases before 3.9.16, 3.16.8, 4.1.3, 4.2.5, 4.3.4, and 4.4.1; Atlassian said Jira Service Desk Cloud and Jira Core or Jira Software deployments without Jira Service Desk were not affected.
Independent analysis showed the traversal could reach administrative portal resources and expose broad issue data through search and export endpoints using JQL, making exploitation especially concerning where self-registration allowed easy portal access. Atlassian urged customers to upgrade immediately and offered temporary mitigations such as blocking requests containing .. at a reverse proxy or load balancer, or adding redirect rules in urlrewrite.xml, while researcher Sam Curry warned that redirect-based defenses might be bypassed through alternate encodings and reported discovering the issue during an Atlassian Bug Bash.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Sam Curry published a detailed analysis showing how traversal requests could bypass portal separation and how Jira search and export endpoints could be used with JQL to retrieve broad issue data. The write-up also questioned whether Atlassian's suggested redirect-based mitigation would fully prevent alternate encodings from reaching administrative endpoints.
Atlassian disclosed CVE-2019-14994 on 2019-09-18, describing it as a critical path traversal vulnerability in Jira Service Desk Server and Data Center. The company released fixed versions 3.9.16, 3.16.8, 4.1.3, 4.2.5, 4.3.4, and 4.4.1, and recommended immediate upgrades or temporary mitigations such as blocking '..' requests.
Sam Curry discovered CVE-2019-14994 during an Atlassian Bug Bash hosted by Bugcrowd. The flaw allowed a user with customer portal access to traverse to administrative portal resources and disclose issue data across Jira projects.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
confluence.atlassian.com
Open sourcesamcurry.net
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Atlassian patched **CVE-2022-26135**, an authenticated server-side request forgery (SSRF) flaw in Jira Core and Jira Service Desk. The issue allowed an attacker to cause a vulnerable Jira instance to send requests to arbitrary URLs with attacker-controlled HTTP methods, headers, and request bodies; deployments with open user registration could be exposed without an attacker first obtaining an account. An attacker could use the flaw to reach internal-only services and, in cloud-hosted environments, query cloud metadata endpoints to obtain sensitive information or potentially cloud credentials. Organizations running affected Jira Server or Data Center deployments should apply Atlassian’s June 2022 security updates and restrict unauthenticated sign-up, while reviewing access to metadata services and internal endpoints from Jira hosts.
Sep 3, 2026
Atlassian disclosed a high-severity file inclusion vulnerability in **Jira Software Data Center** that affects versions `9.17.5` and `11.3.8`. The flaw, tracked in Atlassian's advisory with a **CVSS 4.0 score of 8.8**, could allow an **unauthenticated attacker** to read local files or execute other files already present on the server, creating a significant risk for exposed Jira deployments. Atlassian directed customers to upgrade to a fixed supported release, including **Jira Software Data Center `11.3.10` or later** in the `11.3` branch, or otherwise move to the latest available version. A separate Atlassian notice also states that **Data Center products are scheduled to reach end of life in 2029** as the company shifts focus to cloud offerings, underscoring the need for organizations still running self-managed Jira environments to prioritize remediation and longer-term migration planning.
Aug 19, 2026
Atlassian and Finland’s National Cyber Security Centre warned of multiple severe vulnerabilities in Atlassian products, led by **`CVE-2022-1471`**, a critical SnakeYAML deserialization flaw rated **CVSS 9.8** that can enable remote code execution across **Bitbucket, Confluence, Jira Core, Jira Software, Jira Service Management, Automation for Jira,** and the **Confluence Cloud Migration App**. Atlassian said its hosted **`atlassian.net`** cloud sites are not affected, but Data Center and Server deployments face broad exposure and should be upgraded immediately to fixed releases. The advisories also identified product-specific RCE issues in **Confluence Data Center and Server** (**`CVE-2023-22522`**), the **Assets Discovery** app (**`CVE-2023-22523`**), and **Atlassian Companion App for macOS** (**`CVE-2023-22524`**). Authorities urged organizations to install patched versions without delay and, where patching cannot be completed at once, remove vulnerable services from the public internet; Atlassian added that there is no mitigation for some affected products, while certain Jira and Jira Service Management environments can reduce risk by upgrading the **Automation for Jira** app to a fixed version.
Jun 29, 2026