# CVE-2025-20286: ISE on AWS Static Credential > Unauthenticated attackers can use shared static credentials from cloud deployments to access sensitive data, modify configurations, or disrupt services in Cisco ISE. - **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 4 Jun 2025 - **Updated:** 5 Jun 2025 - **Also known as:** GHSA-mj8j-c9rh-x2c6 ## What is CVE-2025-20286? CVE-2025-20286 is a critical vulnerability in Cisco Identity Services Engine, published on 4 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability in Amazon Web Services (AWS), Microsoft Azure, and Oracle Cloud Infrastructure (OCI) cloud deployments of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to access sensitive data, execute limited administrative operations, modify system configurations, or disrupt services within the impacted systems. This vulnerability exists because credentials are improperly generated when Cisco ISE is being deployed on cloud platforms, resulting in different Cisco ISE deployments sharing the same credentials. These credentials are shared across multiple Cisco ISE deployments as long as the software release and cloud platform are the same. An attacker could exploit this vulnerability by extracting the user credentials from Cisco ISE that is deployed in the cloud and then using them to access Cisco ISE that is deployed in other cloud environments through unsecured ports. A successful exploit could allow the attacker to access sensitive data, execute limited administrative operations, modify system configurations, or disrupt services within the impacted systems. Note: If the Primary Administration node is deployed in the cloud, then Cisco ISE is affected by this vulnerability. If the Primary Administration node is on-premises, then it is not affected. Weakness: CWE-259 (Use of Hard-coded Password) ## Which versions are affected by CVE-2025-20286? It affects 1 product. Products: Cisco Identity Services Engine. ## How do I fix CVE-2025-20286? No fix has been published for CVE-2025-20286 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-20286 being exploited? There is no known exploitation of CVE-2025-20286 in the wild and no public exploit code. ## Other vulnerabilities in Cisco Identity Services Engine - [CVE-2026-76460](https://insights.sbomify.com/CVE-2026-76460/): Cisco Identity Services Engine Incorrect Use of Privileged APIs (critical 10.0, exploited in the wild) - [CVE-2025-20337](https://insights.sbomify.com/CVE-2025-20337/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild) - [CVE-2025-20281](https://insights.sbomify.com/CVE-2025-20281/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild) - [CVE-2026-20130](https://insights.sbomify.com/CVE-2026-20130/): Cisco Identity Services Engine Hardening Release - Improper Neutralization Vulnerabilities (critical 10.0) - [CVE-2026-20192](https://insights.sbomify.com/CVE-2026-20192/): Cisco Identity Services Engine Hardening Release - Access Control Vulnerabilities (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-20286 and fix it if it is affected. What it is: CVE-2025-20286 is a critical vulnerability in Cisco Identity Services Engine, published on 4 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-20286 in the wild and no public exploit code. Affected product: Cisco Identity Services Engine. 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-20286/ (Markdown: https://insights.sbomify.com/CVE-2025-20286/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20286 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20286 - OSV: https://osv.dev/vulnerability/CVE-2025-20286 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-20286/ Summaries are generated and may contain mistakes; the official description above is the record.