dbcve.org
Jira AlignApplication · Atlassian

CVE-2025-22169

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-22
Fix available
A fix is available. Upgrade to 11.16.1 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 subscribe to an item/object without having the expected permission level.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Jira Align contains an authorization bypass where low-privilege users can access unexpected endpoints that disclose limited sensitive information. The specific example demonstrates a low-level user subscribing to an item/object without possessing the expected permission level, indicating broken access control on subscription-related API endpoints.

MitigationApply the vendor patch when released and review user role configurations to ensure principle of least privilege. Audit subscription and notification permissions for all user roles.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jira AlignApplication
Affected:>= 11.14.0, < 11.16.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Jira Align version
    Check the Jira Align version number in the application (typically found in the About or Settings section of the platform)
    Affected if The installed version is 11.14.0 through 11.15.x (versions before 11.16.1)
  2. Verify user role permissions for subscriptions
    Review the permission configuration for low-privilege user roles, specifically around subscription and notification capabilities in the Jira Align admin settings
    Affected if Low-privilege users have permission to access subscription-related API endpoints without proper role-based access controls
  3. Test subscription endpoint accessibility
    Using a low-privilege user account, attempt to access subscription APIs (such as subscribing to items or objects) that should require higher permissions
    Affected if Low-privilege users can successfully subscribe to objects they should not have access to based on their role configuration
  4. Check for unexpected subscription records
    Audit the subscription/notification database or logs for entries created by users with limited roles that are subscribed to objects outside their typical access scope
    Affected if Subscription records exist where the subscribing user role does not match the expected permission level for that object type

A user is affected if running Jira Align version 11.14.0 through 11.15.x and low-privilege accounts can access subscription endpoints that should require elevated permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.16.1 or later
Fixed in 11.16.1
Interim mitigation

Apply the vendor patch when released and review user role configurations to ensure principle of least privilege. Audit subscription and notification permissions for all user roles.

Recommended fix High confidence

Jira Align 11.16.1 or later

  1. Identify the current Jira Align version in use (check System Info or About page)
  2. Schedule a maintenance window for the upgrade
  3. Back up the Jira Align database and configuration files
  4. Upgrade Jira Align to version 11.16.1 or later
  5. Verify the upgrade was successful by checking the version number
  6. Test that the authorization controls are working correctly by verifying low-privilege users can no longer subscribe to items without proper permissions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jira Align Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22169 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22169 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data