Skip to main content

Jira Align CVE-2025-22168

MEDIUM
Improper Authorization (CWE-285)
2025-10-22 security@atlassian.com
5.3
CVSS 4.0 · Vendor: atlassian
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege Jira Align user
  2. Exploit
    Enumerate unexpected/unauthorized endpoints
  3. Execution
    Request another user's private resource (e.g. checklist)
  4. Impact
    Receive disclosed sensitive data

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

Requires a valid authenticated low-privilege account on the target Jira Align instance (PR:L); exploitation is remote over the network (AV:N) with low complexity (AC:L) and no user interaction. The limiting factors are that the attacker must already hold tenant credentials and that each access yields only a small amount of another user's sensitive data (e.g. private checklist steps) - there is no integrity or availability impact and no privilege escalation. No special non-default configuration is named in the advisory.

Impact

This is a genuinely low-risk authorization flaw (CWE-285 improper authorization) despite being an enterprise Atlassian product. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L, score 5.3) and the description agree: an authenticated low-privilege user (PR:L) can reach endpoints that leak a 'small amount of sensitive information' such as another user's private checklist steps - confidentiality-only (VC:L), no integrity or availability impact. EPSS is 0.21% (9th percentile), there is no CISA KEV listing and no public exploit identified at time of analysis, so this is not under active or probable mass exploitation. SSVC-wise: exploitation status is none, technical impact is partial, and automatability is low given it requires valid authenticated access and the payoff is minor data disclosure. The only mild conflict is the input Tag 'Authentication Bypass', which contradicts both the CWE (authorization, not authentication) and the vector (PR:L confirms the attacker is already authenticated) - this is an authorization/IDOR issue, not an auth bypass. Treat as a routine patch-cycle item, not a priority.

Exploit ScenarioDerived

A legitimate low-privilege Jira Align user, already logged into the tenant, manipulates or directly requests endpoints they are not meant to reach (e.g. the checklist of another user) and receives sensitive data belonging to other users. No exploit code is public; exploitation is trivial technically (AC:L) but gated by needing a valid low-privilege account and yields only a small amount of information per request.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 01, 2026

Improper authorization checks in Atlassian Jira Align allow an authenticated low-privilege user to reach endpoints beyond their intended permissions, disclosing small amounts of other users' sensitive data - for example, reading the steps of another user's private checklist. Exploitation requires a valid tenant account (PR:L per the CVSS vector), is remote and low-complexity with no user interaction, and results in only limited confidentiality impact with no integrity, availability, or scope change. Risk is further tempered by a very low EPSS of 0.21% (9th percentile) and no public exploit code or CISA KEV listing identified at time of analysis.

RemediationAI

The authoritative remediation guidance is Atlassian's advisory at https://jira.atlassian.com/browse/JIRAALIGN-8637; the provided data does not specify an exact fixed version, and because Jira Align is a vendor-hosted service, Atlassian applies corrections on the cloud platform, so customers should confirm their tenant's current patch/rollout status through that advisory rather than assume a self-managed upgrade path. Where immediate isolation is needed, reduce exposure by auditing and narrowing Jira Align role assignments so that the lowest-privilege roles genuinely granted are only those users require, and by removing dormant or over-provisioned accounts - the trade-off is reduced end-user functionality for roles that legitimately need broader endpoint access. As a detective compensating control, monitor Jira Align access logs for low-privilege accounts issuing requests to endpoints or objects outside their normal workflow (for example, repeated checklist or user-profile reads belonging to other accounts), since each exploit yields only a small data leak and repeated anomalous reads are the most reliable signal; this monitoring adds log volume and alert-tuning overhead but does not block the underlying weakness. Note that no public exploit code has been identified and EPSS is only 0.21% (9th percentile), so emergency compensating changes are not warranted ahead of the vendor fix.

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): certain endpoints in Jira Align fail to enforce adequate server-side authorization checks, so a user holding only low privileges can request resources and data that should be restricted to higher-privileged or different users. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N) and the independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) agree that the exposure is a bounded confidentiality leak - no write, deletion, privilege escalation, or cross-scope effect is involved. The CPE cpe:2.3:a:atlassian:jira_align:*:*:*:*:*:*:*:* indicates the issue applies across Jira Align releases rather than a single build, consistent with a systemic missing-authorization pattern in the application's endpoint layer rather than a memory-safety or injection defect. Because the data leaked is described as a 'small amount' (e.g., another user's checklist steps), the practical value to an attacker is reconnaissance or targeted information gathering against an organization already holding credentials, not broad compromise.

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

Vendor (atlassian) PRIMARY 5.3 MEDIUM
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
vuln.today AI 4.3 MEDIUM

Authenticated low-privilege user (PR:L) remotely (AV:N) reads limited cross-user data with low complexity; confidentiality-only (C:L), no integrity/availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (atlassian).

CVSS VectorVendor: atlassian

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

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 read the steps of another user's private checklist.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Medium
Atlassian enterprise agile-planning SaaS, deployed but narrower than core Jira
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Affected Products (CPE)CVE.org

cpe:2.3:a:atlassian:jira_align:*:*:*:*:*:*:*:*
CVE-2022-36803 HIGH
8.8 Oct 14

The MasterUserEdit API in Atlassian Jira Align Server before version 10.109.2 allows An authenticated attacker with the

CVE-2025-22178 MEDIUM
5.3 Oct 22

Improper authorization in Atlassian Jira Align allows a remote authenticated low-privilege user to access endpoints outs

CVE-2025-22177 MEDIUM
5.3 Oct 22

Authorization bypass in Atlassian Jira Align allows any authenticated low-privilege user to reach endpoints that should

CVE-2025-22176 MEDIUM
5.3 Oct 22

Authenticated low-privilege users of Atlassian Jira Align can access restricted endpoints and disclose limited sensitive

CVE-2025-22174 MEDIUM
5.3 Oct 22

Improper authorization in Atlassian Jira Align lets a low-privilege authenticated user reach endpoints that should be ga

CVE-2025-22173 MEDIUM
5.3 Oct 22

Improper authorization in Atlassian Jira Align lets an authenticated low-privilege user reach endpoints that fail to enf

CVE-2025-22172 MEDIUM
5.3 Oct 22

Authenticated low-privilege users of Atlassian Jira Align can reach application endpoints they are not authorized to use

CVE-2025-22170 MEDIUM
5.3 Oct 22

Improper authorization in Atlassian Jira Align allows an authenticated low-privilege user to perform actions they are no

CVE-2025-22171 MEDIUM
5.3 Oct 22

Improper authorization in Atlassian Jira Align's checklist feature lets any authenticated user with low privileges modif

CVE-2025-22175 MEDIUM
5.3 Oct 22

Jira Align's broken object-level authorization permits an authenticated low-privilege user to access or modify limited r

CVE-2025-22169 MEDIUM
5.3 Oct 22

Missing per-endpoint authorization checks in Atlassian Jira Align allow any authenticated low-privilege user to reach en

CVE-2022-36802 MEDIUM
4.9 Oct 14

The ManageJiraConnectors API in Atlassian Jira Align before version 10.109.2 allows remote attackers to exploit this iss

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy