Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-22170: Improper Authorization in Atlassian Jira Align

0
Medium
VulnerabilityCVE-2025-22170cvecve-2025-22170
Published: Wed Oct 22 2025 (10/22/2025, 16:30:04 UTC)
Source: CVE Database V5
Vendor/Project: Atlassian
Product: Jira Align

Description

Jira Align is vulnerable to an authorization issue. A low-privilege user without sufficient privileges to perform an action could if they included a particular state-related parameter of a user with sufficient privileges to perform the action.

AI-Powered Analysis

AILast updated: 10/29/2025, 18:15:36 UTC

Technical Analysis

CVE-2025-22170 is an improper authorization vulnerability identified in Atlassian Jira Align, a tool used for agile portfolio management. The flaw arises because the application fails to properly verify whether a user has sufficient privileges to perform certain actions. Specifically, a low-privilege user can include a crafted state-related parameter associated with a higher-privilege user to bypass authorization checks and execute actions they are not permitted to perform. This vulnerability affects Jira Align versions 11.14.0 and above, including 11.14.1, 11.15.0, 11.15.1, and 11.16.0. The vulnerability is remotely exploitable over the network without requiring user interaction, and no authentication beyond low privilege is needed. The CVSS v4.0 base score is 5.3, reflecting medium severity due to the potential for unauthorized actions that could impact data integrity and operational processes but without direct impact on confidentiality or availability. The weakness is classified under CWE-285 (Improper Authorization). No public exploits have been reported yet, and Atlassian has not published patches at the time of this report. The vulnerability could be leveraged by attackers to manipulate project data, change configurations, or perform unauthorized operations within Jira Align, potentially disrupting agile workflows and decision-making processes.

Potential Impact

For European organizations, the impact of CVE-2025-22170 could be significant, especially for those relying heavily on Jira Align for managing complex agile projects and portfolios. Unauthorized actions by low-privilege users could lead to data integrity issues, such as unauthorized changes to project plans, resource allocations, or reporting data, which could cascade into operational inefficiencies or flawed strategic decisions. While the vulnerability does not directly expose sensitive data or cause service outages, the manipulation of project management data can undermine trust in the system and delay critical business processes. Sectors such as finance, telecommunications, manufacturing, and government agencies using Jira Align for agile transformation initiatives may face increased risk. Additionally, the lack of known exploits currently provides a window for proactive mitigation, but organizations should not delay remediation. The medium severity rating suggests a moderate risk, but the potential for insider threats or targeted attacks exploiting this flaw should be considered in risk assessments.

Mitigation Recommendations

Organizations should implement the following specific mitigation strategies: 1) Immediately review and tighten user permissions within Jira Align, ensuring that users have only the minimum necessary privileges. 2) Monitor logs and audit trails for unusual activity, particularly actions performed by low-privilege users that could indicate exploitation attempts. 3) Apply vendor patches and updates as soon as Atlassian releases them for this vulnerability. 4) If patches are not yet available, consider temporary compensating controls such as disabling or restricting access to affected functionalities for low-privilege users. 5) Conduct internal security awareness training to alert administrators and users about the risk of privilege escalation via parameter manipulation. 6) Employ web application firewalls (WAFs) or API gateways to detect and block suspicious parameter tampering attempts. 7) Regularly review and test authorization controls through penetration testing or automated security scanning focused on access control weaknesses. These targeted actions go beyond generic advice by focusing on access control hygiene, monitoring, and layered defenses specific to the nature of this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
atlassian
Date Reserved
2025-01-01T00:01:27.177Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68f90a3b99c688c2fb43c63a

Added to database: 10/22/2025, 4:45:47 PM

Last enriched: 10/29/2025, 6:15:36 PM

Last updated: 10/30/2025, 6:53:49 AM

Views: 54

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats