Vulnerability in Cisco Secure FTD Software (CVE-2026-20017)
Summary
Vulnerability in Cisco Secure FTD Software (CVE-2026-20017). Confidential information can be exposed externally.
Original description
The description as published by the source.
A vulnerability in the CLI of Cisco Secure FTD Software could allow an authenticated, local attacker to execute arbitrary commands on the underlying operating system as root. To exploit this vulnerability, the attacker must have valid administrative credentials on an affected device.
This vulnerability is due to insufficient input validation of user-supplied command arguments. An attacker could exploit this vulnerability by submitting crafted input for a specific CLI command. A successful exploit could allow the attacker to execute commands on the underlying operating system as root.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-20017 has been found in Cisco Secure FTD Software.
Confidential information can be exposed externally. CVSS score: 6.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Cisco Secure FTD Software CVE-2026-20017" on the vendor's site.
CVE-2026-20017 (Cisco Secure FTD Software) — CWE-250 / CVSS v3 6.0
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-250) exists in Cisco Secure FTD Software.
Check the vendor advisory for the affected versions of Cisco Secure FTD Software.
Severity: Medium (CVSS 6.0/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Cisco Secure FTD Software を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch psirt@cisco.com