# CVE-2026-21579: Information disclosure in Confluence Data Center > Unauthenticated attackers can view sensitive information in Confluence Data Center, requiring an upgrade to patched versions. - **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 21 Jul 2026 - **Updated:** 22 Jul 2026 - **Also known as:** GHSA-5vfq-26hx-8v79 ## What is CVE-2026-21579? CVE-2026-21579 is a high-severity vulnerability in Atlassian Confluence Data Center, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description This High severity Information Disclosure vulnerability was introduced in versions 7.17.0, 7.19.0, 8.5.0, 8.9.0, 9.0.1, 9.1.0, 9.2.0, 10.0.2, 10.1.0, and 10.2.0 of Confluence Data Center. This Information Disclosure vulnerability, with a CVSS Score of 8.2, allows an unauthenticated attacker to view sensitive information via an Information Disclosure vulnerability. 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]). This vulnerability was reported via our Atlassian (Internal) program. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2026-21579? It affects 1 product. Products: Atlassian Confluence Data Center. ## How do I fix CVE-2026-21579? No fix has been published for CVE-2026-21579 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-21579 being exploited? There is no known exploitation of CVE-2026-21579 in the wild and no public exploit code. ## Other vulnerabilities in Atlassian Confluence Data Center - [CVE-2023-22527](https://insights.sbomify.com/CVE-2023-22527/): Atlassian Confluence Data Center and Server Template Injection (critical 10.0, exploited in the wild) - [CVE-2023-22518](https://insights.sbomify.com/CVE-2023-22518/): Atlassian Confluence Data Center and Server Improper Authorization (critical 10.0, exploited in the wild) - [CVE-2023-22515](https://insights.sbomify.com/CVE-2023-22515/): Atlassian Confluence Data Center and Server Broken Access Control (critical 10.0, exploited in the wild) - [CVE-2022-26134](https://insights.sbomify.com/CVE-2022-26134/): Atlassian Confluence Server and Data Center Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2021-26084](https://insights.sbomify.com/CVE-2021-26084/): Atlassian Confluence Server and Data Center Object-Graph Navigation Language (OGNL) Injection (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-21579 and fix it if it is affected. What it is: CVE-2026-21579 is a high-severity vulnerability in Atlassian Confluence Data Center, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-21579 in the wild and no public exploit code. Affected product: Atlassian Confluence Data Center. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-21579/ (Markdown: https://insights.sbomify.com/CVE-2026-21579/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-21579 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-21579 - OSV: https://osv.dev/vulnerability/CVE-2026-21579 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-21579/ Summaries are generated and may contain mistakes; the official description above is the record.