dbcve.org
Ios XrOperating system · Cisco

CVE-2025-20363

CRITICAL · 9.0 CVSS v3.1 Published 2025-09-25
Fix available
A fix is available. Upgrade to 7.0.8 / 7.2.10 or later.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Improper validation of user-supplied input in HTTP requests on Cisco ASA, FTD, IOS, IOS XE, and IOS XR web services allows attackers to execute arbitrary code as root. For ASA/FTD, exploitation requires no authentication; for IOS/IOS XR, low-privilege authenticated access is needed.

MitigationApply vendor-provided patches immediately; until patched, restrict access to HTTP web services to trusted networks only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ios XrOperating system
Affected:= 6.5.1= 6.5.2= 6.5.3= 6.6.2= 6.6.3= 6.6.25= 6.7.1= 6.7.2= 6.7.3= 6.8.1= 6.8.2= 6.9.1
Adaptive Security Appliance SoftwareOperating system
Affected:>= 9.12, < 9.12.4.72>= 9.14, < 9.14.4.28>= 9.16, < 9.16.4.84>= 9.17.1, < 9.18.4.57>= 9.19.1, < 9.19.1.42>= 9.20.1, < 9.20.3.16>= 9.22, < 9.22.2>= 9.23, < 9.23.1.3
iOSOperating system
Affected:>= 12.2\(15\)b, <= 15.9\(3\)m11
Ios XeOperating system
Affected:>= 3.2.0sg, <= 17.17.1
Secure Firewall Threat DefenseApplication
Affected:>= 7.0.0, < 7.0.8>= 7.1.0, < 7.2.10>= 7.3.0, < 7.4.2.3>= 7.7.0, < 7.7.10= 7.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Cisco product and version
    Run 'show version' on the device CLI to obtain the exact software version and product model
    Affected if The product is Cisco ASA, FTD, IOS, IOS XE, or IOS XR and the version falls within the affected ranges listed in the CVE
  2. Confirm HTTP server is enabled
    For ASA/FTD, run 'show http server' or check running configuration for 'http server enable'. For IOS/IOS XE, check for 'ip http server' or 'ip http secure-server' in the configuration. For IOS XR, check for 'http server' under the management plane
    Affected if HTTP or HTTPS web services are actively enabled on the device management interface
  3. Verify management interface exposure
    Check access control lists or interface ACLs applied to the management (Mgmt, Management0/0) or inside/outside interfaces to determine if HTTP traffic from untrusted networks can reach the device
    Affected if The HTTP service is reachable from any network other than a strictly controlled management network or localhost
  4. Confirm ASA/FTD HTTP server status specifically
    On ASA/FTD devices, run 'show running-config http' to see if the HTTP server is configured and which IP addresses are permitted
    Affected if HTTP server is enabled and permits connections from non-restricted IP ranges

The device is affected if it runs a vulnerable Cisco ASA, FTD, IOS, IOS XE, or IOS XR version AND has HTTP web services enabled and accessible, allowing remote injection of malicious requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.8 / 7.2.10 / 7.4.2.3 or later
Fixed in 7.0.87.2.107.4.2.3
Interim mitigation

Apply vendor-provided patches immediately; until patched, restrict access to HTTP web services to trusted networks only.

Recommended fix High confidence

ASA: 9.12.4.72+, 9.14.4.28+, 9.16.4.84+, or 9.18.4.57+ | FTD: 7.0.8+, 7.2.10+, 7.4.2.3+, or 7.7.10+ | IOS XE: 17.18.1+ | IOS XR: contact Cisco | iOS: contact Cisco

  1. 1. Identify the affected Cisco product and current version running on the device
  2. 2. For Cisco ASA Software: upgrade to 9.12.4.72 or later, 9.14.4.28 or later, 9.16.4.84 or later, or 9.18.4.57 or later depending on your release train
  3. 3. For Cisco FTD Software: upgrade to 7.0.8 or later, 7.2.10 or later, 7.4.2.3 or later, or 7.7.10 or later depending on your release train
  4. 4. For Cisco IOS XE Software: upgrade to 17.18.1 or later (first fixed release after 17.17.1)
  5. 5. For Cisco IOS XR Software: contact Cisco for specific fixed versions for 6.5.x and 6.6.x releases
  6. 6. For Cisco iOS: contact Cisco for specific fixed versions
  7. 7. Before upgrading, review Cisco release notes for compatibility and any special upgrade instructions
  8. 8. Schedule maintenance window and backup configuration
Caveat Review Cisco release notes for any compatibility alerts, behavior changes, or deprecated features in the target release before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ios Xr Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20363 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20363 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data