Jira Align
CVE-2025-22174
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege account
-
ExploitRequest unauthorized portfolio/room endpoint
-
ExecutionServer fails authorization check
-
ImpactReceive sensitive information disclosure
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization verification
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid authenticated Jira Align account at a low privilege level (PR:L); it is not reachable by fully unauthenticated attackers. The attacker then accesses specific endpoints that lack proper authorization enforcement - the description cites viewing portfolio rooms without the required permission as a concrete example. No user interaction, special configuration, or non-default deployment mode is needed (UI:N, AC:L), and impact is limited to disclosure of a small amount of sensitive information (confidentiality only). The primary limiting factor is the need for prior valid low-privilege credentials, which confines realistic exploitation to insiders, compromised accounts, or multi-tenant environments granting broad low-trust access. |
| Impact | This is a low-to-moderate priority issue that should not be over-prioritized despite its CVSS 5.3 (4.0) rating. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N) shows a network-reachable, low-complexity flaw but one that requires an already-authenticated low-privilege account (PR:L) and yields only low confidentiality impact (VC:L) with zero integrity or availability impact - consistent with the description's 'small amount of sensitive information' disclosure. EPSS is low at 0.21% (10th percentile), there is no CISA KEV listing, and no public exploit was identified, so all exploitation signals point the same direction: no evidence of widespread or opportunistic attack interest. These signals are mutually consistent rather than conflicting. The one cross-source discrepancy is the 'Authentication Bypass' tag, which does not match the CVE's actual nature: both the description and CWE-285 (Improper Authorization) describe a post-authentication access-control/authorization failure, not a bypass of authentication itself. Net assessment: a genuine but limited broken-access-control information-disclosure bug, meaningful for multi-tenant/enterprise Jira Align deployments with many low-trust users, but not an urgent mass-exploitation threat. |
| Exploit ScenarioDerived | An attacker who already holds a legitimate low-privilege Jira Align account (for example, a basic team member) sends requests to endpoints they are not authorized to reach and receives sensitive data - such as viewing portfolio rooms - without the required permission. Because the attack is network-based with low complexity (AV:N/AC:L) but needs valid low-level credentials (PR:L) and no user interaction, exploitation is simple for any insider or compromised account. No public exploit code was identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Improper authorization in Atlassian Jira Align lets a low-privilege authenticated user reach endpoints that should be gated behind higher permissions, exposing a small amount of sensitive information - the vendor cites a low-level user viewing portfolio rooms without the required permission as a concrete case. According to the CVSS vector (PR:L), exploitation requires a valid low-privilege Jira Align account; the issue is not reachable by fully unauthenticated attackers, requires no user interaction or non-default configuration, and is limited to low confidentiality impact with no integrity or availability effect. There is no public exploit code identified and no CISA KEV listing, and the EPSS score of 0.21% (10th percentile) indicates a very low likelihood of exploitation attempts, consistent with an insider- or compromised-account-driven risk rather than an opportunistic remote attack.
RemediationAI
Because Jira Align is an Atlassian-hosted service, the primary fix is applied server-side by Atlassian - track the JIRAALIGN-8643 advisory at https://jira.atlassian.com/browse/JIRAALIGN-8643 to confirm when the authorization fix has been deployed to your tenant; the supplied data does not specify an exact fixed version, so no patch version should be assumed. While waiting, treat this as an identity-and-access exposure rather than a network-perimeter problem: inventory and de-provision dormant or over-broad low-privilege Jira Align accounts (side effect: reduced convenience for occasionally active users who would then need re-request workflows), enforce least privilege on portfolio-room and admin-adjacent permissions, and prefer SSO with strong authentication and session controls so that compromised low-trust credentials are harder to obtain (side effect: added MFA/SSO friction and integration effort). Monitor audit logs for anomalous or unexpected access to portfolio rooms and other privileged endpoints by low-privilege users, since that access pattern is the concrete exploitation signal described by the vendor; detection-only monitoring does not stop the disclosure and is a compensating control, not a substitute for the service-side fix. Restricting tenant membership or segmenting user populations where multi-tenant or high-volume low-trust access exists reduces the blast radius but may conflict with business requirements for broad read access.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-285 (Improper Authorization): specific Jira Align endpoints fail to enforce the permission checks that the application's intended authorization model requires, so an authenticated principal with only low privileges can reach data scoped for higher-privileged roles. This is a missing/incorrect authorization-control failure rather than an authentication bypass - the attacker must already hold a legitimate, low-privilege identity in the tenant, which moves the realistic threat model toward insiders, compromised low-trust accounts, or broadly provisioned multi-tenant user bases. Atlassian's own CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N) and the independent CVSS 3.1 reassessment (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) agree on the shape of the issue: network-reachable, low attack complexity, low-privilege prerequisite, no user interaction, and a confidentiality-only impact with no scope change. The CPE entry cpe:2.3:a:atlassian:jira_align:*:*:*:*:*:*:*:* uses a wildcard version, and since Jira Align is delivered as an Atlassian-hosted service, remediation is applied server-side by Atlassian rather than by the customer running a local patch; the underlying weakness class (broken object/function-level authorization on per-endpoint permission checks) is the same class that routinely appears in SaaS administrative interfaces when new endpoints are added without parity to existing permission gates.
Know when Jira Align gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Network-reachable but requires an authenticated low-privilege account (PR:L) and no user interaction; only limited information disclosure, so C:L with I:N and A:N.
Primary rating from Vendor (atlassian).
CVSS VectorVendor: atlassian
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Affected Products (CPE)CVE.org
More in Jira Align
View allThe MasterUserEdit API in Atlassian Jira Align Server before version 10.109.2 allows An authenticated attacker with the
Improper authorization in Atlassian Jira Align allows a remote authenticated low-privilege user to access endpoints outs
Authorization bypass in Atlassian Jira Align allows any authenticated low-privilege user to reach endpoints that should
Authenticated low-privilege users of Atlassian Jira Align can access restricted endpoints and disclose limited sensitive
Improper authorization in Atlassian Jira Align lets an authenticated low-privilege user reach endpoints that fail to enf
Authenticated low-privilege users of Atlassian Jira Align can reach application endpoints they are not authorized to use
Improper authorization in Atlassian Jira Align allows an authenticated low-privilege user to perform actions they are no
Improper authorization checks in Atlassian Jira Align allow an authenticated low-privilege user to reach endpoints beyon
Improper authorization in Atlassian Jira Align's checklist feature lets any authenticated user with low privileges modif
Jira Align's broken object-level authorization permits an authenticated low-privilege user to access or modify limited r
Missing per-endpoint authorization checks in Atlassian Jira Align allow any authenticated low-privilege user to reach en
The ManageJiraConnectors API in Atlassian Jira Align before version 10.109.2 allows remote attackers to exploit this iss
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB