dbcve.org
Confluence Data CenterApplication · Atlassian

CVE-2025-22166

HIGH · 7.5 CVSS v3.1 Published 2025-10-21
Fix available
A fix is available. Upgrade to 8.5.25 / 9.2.7 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 DoS (Denial of Service) vulnerability was introduced in version 2.0 of Confluence Data Center. This DoS (Denial of Service) vulnerability, with a CVSS Score of 8.3, allows an attacker to cause a resource to be unavailable for its intended users by temporarily or indefinitely disrupting services of a host connected to a network. 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 and Server 8.5: Upgrade to a release greater than or equal to 8.5.25 Confluence Data Center and Server 9.2: Upgrade to a release greater than or equal to 9.2.7 Confluence Data Center and Server 10.0: Upgrade to a release greater than or equal to 10.0.2 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

CVE-2025-22166 is a high-severity Denial of Service (DoS) vulnerability in Atlassian Confluence Data Center introduced in version 2.0. The vulnerability allows an attacker to disrupt services and make resources unavailable to legitimate users.

MitigationUpgrade Confluence Data Center/Server to one of the supported fixed versions: 8.5.25+, 9.2.7+, or 10.0.2+ as appropriate for your deployment.

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:>= 8.5.0, < 8.5.25>= 9.2.0, < 9.2.7>= 10.0.0, < 10.0.2
Confluence ServerApplication
Affected:>= 8.5.0, < 8.5.25>= 9.2.0, < 9.2.7>= 10.0.0, < 10.0.2

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
None
Integrity
None
Availability
High

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

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. Identify Confluence installation version
    Log into the Confluence administrative console and navigate to the 'About' or 'General Configuration' section to view the installed version number. Alternatively, check the confluence.cfg.xml file in the <confluence-home>/confluence.cfg.xml or look at the WAR application version in the administration panel.
    Affected if The displayed version falls within any of these ranges: 8.5.0 through 8.5.24, 9.2.0 through 9.2.6, or 10.0.0 through 10.0.1
  2. Confirm product deployment type
    Determine whether your Confluence instance is deployed as Data Center or Server. This is typically visible in the administration console header or in the 'Licensing' section.
    Affected if The deployment is Confluence Data Center or Confluence Server and the version matches the affected ranges in step 1
  3. Verify the application is accessible and running
    Attempt to access the Confluence login page or an existing page within the application to confirm the service is currently operational.
    Affected if The application is running and accessible, as this DoS vulnerability affects the availability of a running Confluence instance

You are affected if your Confluence Data Center or Server version is 8.5.0-8.5.24, 9.2.0-9.2.6, or 10.0.0-10.0.1.

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 8.5.25 / 9.2.7 / 10.0.2 or later
Fixed in 8.5.259.2.710.0.2
Interim mitigation

Upgrade Confluence Data Center/Server to one of the supported fixed versions: 8.5.25+, 9.2.7+, or 10.0.2+ as appropriate for your deployment.

Recommended fix High confidence

8.5.25 or later, 9.2.7 or later, or 10.0.2 or later (depending on your current major version)

  1. Back up your Confluence database and home directory before upgrading
  2. Review the Confluence upgrade guide and release notes for the target version
  3. Ensure your system meets the requirements for the target version (8.5.25+, 9.2.7+, or 10.0.2+)
  4. Download the appropriate Confluence installation file for your target version from the Atlassian download center
  5. Stop the Confluence service
  6. Run the installer or extract the new version to replace the existing installation
  7. Start the Confluence service and verify the upgrade completed successfully
  8. Monitor logs for any post-upgrade issues
Caveat Review release notes for breaking changes between your current version and target version before upgrading

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

Fix this in Confluence Data Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22166 — 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-2025-22166 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