# CVE-2026-20151: Cisco Smart Software Manager On-Prem Privilege Escalation Vulnerability > Authenticated attackers can elevate privileges to administrative level by retrieving session credentials from status messages in Cisco SSM On-Prem. - **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 1 Apr 2026 - **Updated:** 2 Apr 2026 - **Also known as:** GHSA-753x-3fmj-hv4q ## What is CVE-2026-20151? CVE-2026-20151 is a high-severity vulnerability in Cisco Smart Software Manager On-Prem, published on 1 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description A vulnerability in the web interface of Cisco Smart Software Manager On-Prem (SSM On-Prem) could allow an authenticated, remote attacker to elevate privileges on an affected system. This vulnerability is due to the improper transmission of sensitive user information. An attacker could exploit this vulnerability by sending a crafted message to an affected Cisco SSM On-Prem host and retrieving session credentials from subsequent status messages. A successful exploit could allow the attacker to elevate privileges on the affected system from low to administrative. To exploit this vulnerability, the attacker must have valid credentials for a user account with at least the role of System User. Note: This vulnerability exposes information only about users who logged in to the Cisco SSM On-Prem host using the web interface and who are currently logged in. SSH sessions are not affected. Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data) ## Which versions are affected by CVE-2026-20151? It affects 1 product. Products: Cisco Smart Software Manager On-Prem. ## How do I fix CVE-2026-20151? No fix has been published for CVE-2026-20151 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-20151 being exploited? There is no known exploitation of CVE-2026-20151 in the wild and no public exploit code. ## Other vulnerabilities in Cisco Smart Software Manager On-Prem - [CVE-2024-20419](https://insights.sbomify.com/CVE-2024-20419/): Auth bypass in Cisco Smart Software Manager On-Prem (critical 10.0) - [CVE-2026-20160](https://insights.sbomify.com/CVE-2026-20160/): Cisco Smart Software Manager On-Prem Arbitrary Command Execution Vulnerability (critical 9.8) - [CVE-2020-3158](https://insights.sbomify.com/CVE-2020-3158/): Cisco Smart Software Manager On-Prem Static Default Credential Vulnerability (critical 9.8) - [CVE-2020-3443](https://insights.sbomify.com/CVE-2020-3443/): Cisco Smart Software Manager On-Prem Privilege Escalation Vulnerability (high 8.8) - [CVE-2019-16029](https://insights.sbomify.com/CVE-2019-16029/): Cisco Smart Software Manager On-Prem Web Interface Denial of Service Vulnerability (high 8.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-20151 and fix it if it is affected. What it is: CVE-2026-20151 is a high-severity vulnerability in Cisco Smart Software Manager On-Prem, published on 1 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-20151 in the wild and no public exploit code. Affected product: Cisco Smart Software Manager On-Prem. 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-20151/ (Markdown: https://insights.sbomify.com/CVE-2026-20151/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-20151 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-20151 - OSV: https://osv.dev/vulnerability/CVE-2026-20151 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-20151/ Summaries are generated and may contain mistakes; the official description above is the record.