Denial of Service (DoS) tar Dependency in Confluence Data Center

XMLWordPrintable

    • Type: Public Security Vulnerability
    • Resolution: Fixed
    • Priority: High
    • 10.2.14, 9.2.22
    • Affects Version/s: 8.9.0, 8.9.1, 8.9.2, 8.9.3, 8.9.4, 9.1.0, 9.0.1, 8.9.5, 9.0.3, 8.9.6, 8.9.7, 9.1.1, 8.9.8, 9.2.5, 9.2.6, 9.5.1, 9.5.2, 9.5.3, 9.2.7, 9.2.8, 9.5.4, 9.2.9, 10.2.0, 9.2.10, 10.1.2, 9.2.11, 9.2.12, 10.2.1, 9.2.13, 10.2.2, 9.2.14, 10.2.3, 9.2.15, 10.2.6, 9.2.17, 10.2.7, 10.2.11, 9.2.20, 9.2.21, 10.2.13
    • Component/s: None
    • 8.7
    • High
    • CVE-2026-59874
    • Atlassian (Internal)
    • CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
    • DoS (Denial of Service)
    • Confluence Data Center

      This High severity DoS (Denial of Service) vulnerability was introduced in versions 8.9.0, 9.0.1, 9.1.0, 9.2.5, 9.5.1, 10.1.2 and 10.2.0 of Confluence Data Center.

      This DoS (Denial of Service) vulnerability, with a CVSS Score of 8.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
      allows an unauthenticated attacker to perform actions as another user which has high impact to confidentiality, high impact to integrity, no impact to availability, and requires no user interaction.

      Atlassian recommends that Confluence 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:

      Confluence Data Center 9.2: Upgrade to a release greater than or equal to 9.2.22

      Confluence Data Center 10.2: Upgrade to a release greater than or equal to 10.2.14

      See the release notes (https://confluence.atlassian.com/doc/confluence-release-notes). You can download the latest version of Confluence Data Center from the download center (https://www.atlassian.com/software/confluence/download-archives).

      The National Vulnerability Database provides the following description for this vulnerability: node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.18, tar.replace accepts a checksum-valid tar header with a negative base-256 encoded entry size, causing the archive scanner to make no progress while repeatedly parsing the same header. This issue is fixed in version 7.5.18.

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

                Created:
                Updated:
                Resolved: