dbcve.org
Confluence Data CenterApplication · Atlassian

CVE-2026-21579

HIGH · 7.5 CVSS v3.1 Published 2026-07-21
Fix available
A fix is available. Upgrade to after 10.2.13 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 4 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an Information Disclosure vulnerability in Atlassian Confluence Data Center affecting multiple versions from 7.17.0 through 10.2.0. The flaw allows an unauthenticated attacker (without credentials) to view sensitive information within the Confluence system.

MitigationUpgrade Confluence Data Center to version 9.2.22 or later, or version 10.2.14 or later. For organizations unable to upgrade immediately, apply the latest supported fixed version appropriate to their current major release line.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Confluence Data CenterApplication
Affected:>= 7.19.26, <= 7.19.30>= 8.5.14, <= 8.5.31>= 8.9.5, <= 8.9.8>= 9.0.1, <= 9.0.3>= 9.1.0, <= 9.1.1>= 9.2.0, <= 9.2.21>= 10.0.2, <= 10.0.3>= 10.1.0, <= 10.1.2>= 10.2.0, <= 10.2.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Confluence Data Center edition
    Access the Confluence administration console or check the product name displayed in the Confluence About page (typically at /about.confluence). Confirm the installation is 'Data Center' and not 'Cloud' or 'Server'.
    Affected if The product is Confluence Data Center (not Confluence Cloud or Confluence Server)
  2. Identify installed Confluence version
    Navigate to the Confluence About page (usually /about.confluence) or check the 'Confluence Administration' > 'General Configuration' section to find the exact version number.
    Affected if The installed version falls within 7.17.0 through 10.2.0 inclusive
  3. Check if unauthenticated access is permitted
    Verify the Confluence configuration for 'Allow public access' or 'Anonymous Access' settings in Confluence Administration under 'Security Configuration'. The vulnerability allows unauthenticated access to sensitive information.
    Affected if Anonymous or public access is enabled on the Confluence instance
  4. Inspect Confluence configuration files
    Examine the confluence.cfg.xml configuration file (located in the Confluence home directory) for any exposed or non-default security settings related to unauthenticated endpoints.
    Affected if Non-default configurations permit unauthenticated access to sensitive endpoints

The environment is affected if Confluence Data Center is running version 7.17.0 through 10.2.0 and unauthenticated or anonymous access is enabled, allowing remote attackers to view sensitive information without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 10.2.13
Interim mitigation

Upgrade Confluence Data Center to version 9.2.22 or later, or version 10.2.14 or later. For organizations unable to upgrade immediately, apply the latest supported fixed version appropriate to their current major release line.

Recommended fix High confidence

Confluence Data Center 9.2.22+ or 10.2.14+ (latest releases recommended)

  1. 1. Backup your Confluence Data Center instance and database before proceeding with any upgrade
  2. 2. Identify your current Confluence Data Center version (check the Atlassian administration console or confluence version on disk)
  3. 3. If running Confluence 9.2.x: upgrade to Confluence Data Center version 9.2.22 or later (recommended: latest 9.2.x release)
  4. 4. If running Confluence 10.2.x: upgrade to Confluence Data Center version 10.2.14 or later (recommended: latest 10.2.x release)
  5. 5. If running older versions (7.x or 8.x): upgrade to the nearest supported version listed above, then proceed to the latest 9.2.x or 10.2.x release
  6. 6. Test the upgrade in a staging environment before applying to production
  7. 7. After upgrade, verify the instance is running and accessible
  8. 8. Review Confluence release notes for any additional post-upgrade configuration requirements
Caveat Review Atlassian release notes for potential breaking changes between your current version and target version; major version upgrades may require migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Confluence Data Center Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21579 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21579 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data