RCE (Remote Code Execution) form-data Dependency in Confluence Data Center

XMLWordPrintable

    • Type: Public Security Vulnerability
    • Resolution: Fixed
    • Priority: High
    • 10.2.14, 9.2.22
    • Affects Version/s: 9.1.0, 9.0.1, 9.0.3, 9.1.1, 9.2.0, 9.2.1, 9.4.0, 9.3.1, 9.2.2, 9.3.2, 9.2.3, 9.4.1, 9.2.4, 9.2.5, 9.2.6, 9.5.1, 9.5.2, 9.5.3, 9.2.7, 10.1.0, 9.2.8, 10.0.2, 10.0.3, 9.5.4, 9.2.9, 10.1.1, 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, 9.2.19, 10.2.10, 10.2.11, 9.2.20, 9.2.21, 10.2.13
    • Component/s: None
    • 8.7
    • High
    • CVE-2026-12143
    • Atlassian (Internal)
    • CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
    • RCE (Remote Code Execution)
    • Confluence Data Center

      This High severity RCE (Remote Code Execution) vulnerability was introduced in versions 9.0.1, 9.1.0, 9.2.0, 9.3.1, 9.4.0, 9.5.1, 10.0.2, 10.1.0, and 10.2.0 of Confluence Data Center.

      This RCE (Remote Code Execution) 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:H/VA:N/SC:N/SI:N/SA:N allows an unauthenticated attacker to execute arbitrary code.

      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-327.html). 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: form-data is a library for creating readable multipart/form-data streams. In versions through 4.0.5, the `field` argument to `FormData#append` and the `filename` option are concatenated verbatim into the `Content-Disposition` header without escaping carriage return (CR), line feed (LF), or double-quote (") characters. An application that passes attacker-controlled data as a field name or filename (for example, an API gateway that turns JSON object keys into multipart field names) allows the attacker to terminate the header line and inject additional headers, or to smuggle entire additional multipart parts, into the request the application forwards to a backend. This can let the attacker add or override form fields (e.g. set `is_admin=true`) seen by the downstream parser. This is an instance of CWE-93 (CRLF injection). The fix escapes CR, LF, and `"` as `%0D`, `%0A`, and `%22` in field names and filenames, matching the serialization browsers use per the WHATWG HTML multipart/form-data encoding algorithm. Exploitation requires the consuming application to use untrusted input as a field name or filename; applications that use only fixed/trusted field names are not affected. Fixed in 2.5.6, 3.0.5, and 4.0.6.

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

                Created:
                Updated:
                Resolved: