# CVE-2025-20363: Memory corruption in Cisco Adaptive Security Appliance (ASA) Software > Remote attackers can execute arbitrary code as root on Cisco network devices via crafted HTTP requests due to improper input validation. - **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/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:** 25 Sep 2025 - **Updated:** 26 Feb 2026 - **Also known as:** GHSA-8wv4-73v4-qxp2 ## What is CVE-2025-20363? CVE-2025-20363 is a critical memory corruption vulnerability in Cisco Adaptive Security Appliance Software, published on 25 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability in the web services of Cisco Secure Firewall Adaptive Security Appliance (ASA) Software, Cisco Secure Firewall Threat Defense (FTD) Software, Cisco IOS Software, Cisco IOS XE Software, and Cisco IOS XR Software could allow an unauthenticated, remote attacker (Cisco ASA and FTD Software) or authenticated, remote attacker (Cisco IOS, IOS XE, and IOS XR Software) with low user privileges to execute arbitrary code on an affected device. This vulnerability is due to improper validation of user-supplied input in HTTP requests. An attacker could exploit this vulnerability by sending crafted HTTP requests to a targeted web service on an affected device after obtaining additional information about the system, overcoming exploit mitigations, or both. A successful exploit could allow the attacker to execute arbitrary code as root, which may lead to the complete compromise of the affected device. For more information about this vulnerability, see the Details ["#details"] section of this advisory. Weakness: CWE-122 (Heap-based Buffer Overflow) ## Which versions are affected by CVE-2025-20363? It affects 5 products. Products: Cisco Adaptive Security Appliance Software, Cisco Ios, Cisco Ios Xe, Cisco Ios Xr, Cisco Secure Firewall Threat Defense. ## How do I fix CVE-2025-20363? No fix has been published for CVE-2025-20363 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-20363 being exploited? There is no known exploitation of CVE-2025-20363 in the wild and no public exploit code. ## Other vulnerabilities in Cisco Adaptive Security Appliance Software - [CVE-2025-20333](https://insights.sbomify.com/CVE-2025-20333/): Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) Buffer Overflow (critical 9.9, exploited in the wild) - [CVE-2016-6366](https://insights.sbomify.com/CVE-2016-6366/): Cisco Adaptive Security Appliance (ASA) SNMP Buffer Overflow (high 8.8, exploited in the wild) - [CVE-2026-20349](https://insights.sbomify.com/CVE-2026-20349/): Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) Heap Inspection (high 8.6, exploited in the wild) - [CVE-2024-20353](https://insights.sbomify.com/CVE-2024-20353/): Cisco ASA and FTD Denial of Service (high 8.6, exploited in the wild) - [CVE-2016-6367](https://insights.sbomify.com/CVE-2016-6367/): Cisco Adaptive Security Appliance (ASA) CLI Remote Code Execution (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-20363 and fix it if it is affected. What it is: CVE-2025-20363 is a critical memory corruption vulnerability in Cisco Adaptive Security Appliance Software, published on 25 Sep 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-20363 in the wild and no public exploit code. Affected product: Cisco Adaptive Security Appliance Software. 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-20363/ (Markdown: https://insights.sbomify.com/CVE-2025-20363/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20363 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20363 - OSV: https://osv.dev/vulnerability/CVE-2025-20363 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-20363/ Summaries are generated and may contain mistakes; the official description above is the record.