-
Type:
Public Security Vulnerability
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 10.1.1, 10.2.0, 10.3.0, 10.3.1, 10.3.2, 10.3.3, 10.3.4, 10.3.5, 10.3.6, 10.3.7, 10.3.8, 10.3.9, 10.3.10, 10.3.11, 10.3.12, 10.3.13, 10.3.14, 10.3.15, 10.4.0, 10.5.0, 10.6.0, 10.7.1, 11.0.0, 11.1.0, 11.2.0, 11.3.0, 11.3.1, 11.3.2, 11.3.3, 11.3.4, 11.3.5, 11.3.6, 11.3.7, 10.3.16, 10.3.17, 10.3.18, 10.3.19, 10.3.20, 10.3.21, 10.3.22, 10.3.23, 10.3.24
-
Component/s: Security
-
7.4
-
High
-
CVE-2026-73086
-
Atlassian (Internal)
-
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
-
CSRF (Cross-Site Request Forgery)
-
Jira Software Data Center
This High severity CSRF (Cross-Site Request Forgery) vulnerability was introduced in versions 10.1.1, 10.2.0, 10.3.0, 10.4.0, 10.5.0, 10.6.0, 10.7.1, 11.0.0, 11.1.0, 11.2.0, and 11.3.0 of Jira Software Data Center.
This CSRF (Cross-Site Request Forgery) vulnerability, with a CVSS Score of 7.4 and a CVSS Vector of CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N allows an unauthenticated attacker to force a end user to execute unwanted actions on a web application in which they're currently authenticated which has high impact to confidentiality, high impact to integrity, no impact to availability, and requires no user interaction.
Atlassian recommends that Jira Software Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:
- Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.25
- Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.8
See the release notes (https://www.atlassian.com/software/jira/download-archives). You can download the latest version of Jira Software Data Center from the download center (https://www.atlassian.com/software/jira/download-archives).
The National Vulnerability Database provides the following description for this vulnerability: nanoid is a secure, URL-friendly, unique string ID generator for JavaScript. Prior to versions 3.3.12 and 5.1.11, the nanoid(size) function in index.js and index.cjs coerces the user-influenced size parameter to a signed 32-bit integer, allowing a value of 2147483648 to become -2147483648 and corrupt the process-wide CSPRNG poolOffset in fillPool(), which causes subsequent session tokens, CSRF tokens, API keys, and unique identifiers to become the deterministic string "uuuuuuuuuuuuuuuuuuuuu" until the process restarts. This issue is fixed in versions 3.3.12 and 5.1.11.