SSRF (Server-Side Request Forgery) fast-uri Dependency in Jira Software Data Center

XMLWordPrintable

    • 7.5
    • High
    • CVE-2026-75899
    • Atlassian (Internal)
    • CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
    • SSRF (Server-Side Request Forgery)
    • Jira Software Data Center

      This High severity SSRF (Server-Side Request Forgery) vulnerability was introduced in version 10.3.23 of Jira Software Data Center.

      This SSRF (Server-Side Request Forgery) vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N allows an unauthenticated attacker to access the content of internal network resources. When running in an environment like Amazon EC2, this flaw may be used to access a metadata resource that provides access credentials and other potentially confidential information which has no 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

      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: fast-uri is a URI parser for Node.js. It decodes percent escapes in a hostname during parsing and then decodes the parsed hostname a second time during authority recomposition, so a single call to normalize or resolve can turn nested percent-encoded input into a different network destination such as a loopback hostname or address. For example, a doubly encoded host that spells out a loopback name decodes to that live host in one operation, which contradicts RFC 3986 section 2.4 that an implementation must not decode the same string more than once. An application that normalizes or resolves an untrusted HTTP-family URI before outbound routing, redirect validation, or a host-policy check can receive a destination different from the one the original encoded host represented, giving a server-side request forgery and host-policy bypass primitive. This is an incomplete-fix variant of CVE-2026-6322. The affected versions are 2.4.1 up to but not including 2.4.5, 3.1.2 up to but not including 3.1.6, and 4.0.0 up to but not including 4.1.3. The issue is fixed in 2.4.5, 3.1.6, and 4.1.3, which normalize percent escapes once and preserve encoded percent signs. Users should upgrade to a patched version.

              Assignee:
              Unassigned
              Reporter:
              Security Metrics Bot
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: