CVE-2025-22174VulnerabilityPublished 22 Oct 2025

CVE-2025-22174: Atlassian Jira Align · Improper Authorization

Affects Atlassian Jira AlignSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Atlassian Jira Align	Affected >=11.14.0 >=11.14.1 >=11.15.0 >=11.15.1 >=11.16.0	Fixed in–

AI-suggested

1. Immediately review and tighten user access controls within Jira Align, ensuring that low-privilege users have no access to sensitive portfolio rooms or restricted endpoints. 2. Implement network segmentation and firewall rules to limit access to Jira Align interfaces only to trusted internal networks and users. 3. Enable detailed logging and monitoring of access to portfolio rooms and other sensitive endpoints to detect unusual access patterns. 4. Coordinate with Atlassian to track the release of official patches addressing CVE-2025-22174 and apply them promptly once available. 5. Conduct internal audits of user roles and permissions regularly to prevent privilege creep. 6. Consider deploying web application firewalls (WAFs) with custom rules to block unauthorized API calls targeting portfolio room endpoints. 7. Educate administrators and users about the risk of unauthorized data exposure and encourage reporting of suspicious activity. 8. If feasible, temporarily restrict access to portfolio rooms to only essential personnel until patches are applied. 9. Review integration points and APIs for similar authorization weaknesses to prevent lateral exploitation.

Description

Jira Align is vulnerable to an authorization issue. A low-privilege user can access unexpected endpoints that disclose a small amount of sensitive information. For example, a low-level user was able to view portfolio rooms without the required permission.

Impact

For European organizations, the impact primarily involves unauthorized disclosure of sensitive project and portfolio information managed within Jira Align. This could lead to exposure of strategic business plans, resource allocations, and other confidential data, potentially benefiting competitors or threat actors conducting espionage. While the vulnerability does not allow modification or deletion of data, the leakage of sensitive information can undermine organizational confidentiality and decision-making. Industries such as finance, manufacturing, and government entities using Jira Align for agile planning may face increased risk of information leakage. The medium severity score reflects that while the impact is limited to confidentiality, the ease of exploitation (network accessible, no user interaction) increases risk. Organizations with extensive use of Jira Align across multiple teams may experience broader exposure. Additionally, unauthorized access could facilitate further attacks by providing attackers with insight into organizational structure and project priorities.

Summary

CVE-2025-22174 is an improper authorization vulnerability identified in Atlassian Jira Align, a widely used enterprise agile planning tool. The flaw stems from insufficient access control checks on certain API endpoints, allowing users with low privileges to access data typically restricted to higher privilege roles. Specifically, low-level users can view portfolio rooms, which may contain sensitive project and organizational information. The 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 CVSS 4.0 base score is 5.3 (medium severity), reflecting network exploitability without authentication or user interaction, but limited confidentiality impact. The weakness corresponds to CWE-285 (Improper Authorization). No patches have been released yet, and no exploits are known in the wild. The issue could allow unauthorized data exposure, potentially aiding attackers in reconnaissance or lateral movement within an organization. Given Jira Align’s role in managing strategic projects and portfolios, unauthorized access could reveal sensitive business information. The vulnerability does not affect system integrity or availability directly but undermines trust in access controls. Organizations should prioritize monitoring and restrict user privileges as a temporary mitigation.

CWE-285Improper Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Cross Zone Scripting (opens in a new tab)
Directory Indexing (opens in a new tab)
Subverting Environment Variable Values (opens in a new tab)
Using Malicious Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jira.atlassian.com/browse/JIRAALIGN-8643 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2025, 18:14 UTC

WeaknessesCWE-285

Technical details

References

Community reviews

Related threats