# CVE-2025-22166: Denial of service in Confluence Data Center > An attacker can disrupt Confluence Data Center services, causing denial of service for intended users. - **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 21 Oct 2025 - **Updated:** 21 Oct 2025 - **Also known as:** GHSA-879m-mhmf-vg5r ## What is CVE-2025-22166? CVE-2025-22166 is a high-severity denial of service vulnerability in Atlassian Confluence Data Center, published on 21 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-405 (Asymmetric Resource Consumption (Amplification)) ## Which versions are affected by CVE-2025-22166? It affects 2 products. Products: Atlassian Confluence Data Center, Atlassian Confluence Server. ## How do I fix CVE-2025-22166? No fix has been published for CVE-2025-22166 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-22166 being exploited? There is no known exploitation of CVE-2025-22166 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-2025-22166 and fix it if it is affected. What it is: CVE-2025-22166 is a high-severity denial of service vulnerability in Atlassian Confluence Data Center, published on 21 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-22166 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-2025-22166/ (Markdown: https://insights.sbomify.com/CVE-2025-22166/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22166 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22166 - OSV: https://osv.dev/vulnerability/CVE-2025-22166 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-22166/ Summaries are generated and may contain mistakes; the official description above is the record.