# CVE-2026-20230: Cisco Unified Communications Manager Server-Side Request Forgery (SSRF) > Unauthenticated attackers can exploit SSRF in Cisco Unified CM to write files and escalate privileges to root if WebDialer is enabled. - **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N`) - **Exploited in the wild:** Yes, since 25 Jun 2026 (CISA KEV) - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 3 Jun 2026 - **Updated:** 7 Oct 2026 - **Also known as:** GHSA-fcv7-pchj-75c2 ## What is CVE-2026-20230? CVE-2026-20230 is a high-severity server-side request forgery vulnerability in Cisco Unified Communications Manager, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability in Cisco Unified Communications Manager (Unified CM) and Cisco Unified Communications Manager Session Management Edition (Unified CM SME) could allow an unauthenticated, remote attacker to conduct server-side request forgery (SSRF) attacks through an affected device. This vulnerability is due to improper input validation for specific HTTP requests. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to write files to the underlying operating system that could be used later to elevate to root. Note: Cisco has assigned this security advisory a Security Impact Rating (SIR) of Critical rather than High as the score indicates. The reason is that exploitation of this vulnerability could result in an attacker elevating privileges to root. Note: To exploit this vulnerability, the WebDialer service must be enabled. WebDialer is disabled by default. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2026-20230? It affects 1 product. Products: Cisco Unified Communications Manager. ## How do I fix CVE-2026-20230? No fix has been published for CVE-2026-20230 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 28 Jun 2026. ## Is CVE-2026-20230 being exploited? Yes. Attackers have exploited CVE-2026-20230 in the wild since at least 25 Jun 2026. Public exploit code: - CVE-2026-20230 - Cisco Unified CM (github_poc): https://github.com/HORKimhab/CVE-2026-20230 - https://github.com/W5M1n9/Cisco-Unified-Communications-Manager-Server-Side-Forgery-Request-Vulnerability-CVE-2026-20230 (github_poc): https://github.com/W5M1n9/Cisco-Unified-Communications-Manager-Server-Side-Forgery-Request-Vulnerability-CVE-2026-20230 - Cisco Unified Communications Manager (Unified CM) deployments affected by CVE-2026-20230. (github_poc): https://github.com/HalilDeniz/CVE-2026-20230-Scanner ## Other vulnerabilities in Cisco Unified Communications Manager - [CVE-2026-20045](https://insights.sbomify.com/CVE-2026-20045/): Cisco Unified Communications Products Code Injection (high 8.2, exploited in the wild) - [CVE-2025-20309](https://insights.sbomify.com/CVE-2025-20309/): Cisco Unified Communications Manager Static SSH Credentials Vulnerability (critical 10.0) - [CVE-2011-1643](https://insights.sbomify.com/CVE-2011-1643/): Information disclosure in n/a (critical 10.0) - [CVE-2024-20253](https://insights.sbomify.com/CVE-2024-20253/): Deserialization in Cisco Packaged Contact Center Enterprise (critical 9.9) - [CVE-2009-0632](https://insights.sbomify.com/CVE-2009-0632/): Information disclosure in n/a (critical 9.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-20230 and fix it if it is affected. What it is: CVE-2026-20230 is a high-severity server-side request forgery vulnerability in Cisco Unified Communications Manager, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2026-20230 in the wild since at least 25 Jun 2026. Affected product: Cisco Unified Communications Manager. 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-20230/ (Markdown: https://insights.sbomify.com/CVE-2026-20230/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-20230 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-20230 - OSV: https://osv.dev/vulnerability/CVE-2026-20230 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-20230/ Summaries are generated and may contain mistakes; the official description above is the record.