dbcve.org
Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2026-20102

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-04
Fix available
A fix is available. Upgrade to 7.0.9 / 7.2.11 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 SAML 2.0 single sign-on (SSO) feature of Cisco Secure Firewall ASA Software and Cisco Secure Firewall Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against the SAML feature and access sensitive, browser-based information. This vulnerability is due to insufficient input validation of multiple HTTP parameters. An attacker could exploit this vulnerability by persuading a user to access a malicious link. A successful exploit could allow the attacker to conduct a reflected XSS attack through an affected device.

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

A reflected cross-site scripting (XSS) vulnerability exists in the SAML 2.0 single sign-on feature of Cisco Secure Firewall ASA and FTD software due to insufficient input validation of HTTP parameters. An unauthenticated remote attacker can exploit this by tricking a user into clicking a malicious link, allowing execution of arbitrary JavaScript in the user's browser to steal sensitive browser-based information such as session cookies or tokens.

MitigationApply the vendor-provided Cisco software patches when available. Until then, consider disabling SAML SSO if not essential, implement WAF rules to filter malicious URL parameters, and educate users about avoiding suspicious links.

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
Adaptive Security Appliance SoftwareOperating system
Affected:>= 9.16.1, < 9.16.4.89>= 9.17.1, < 9.18.4.71>= 9.20.1, < 9.20.4.19>= 9.22.1.1, < 9.22.2.32>= 9.23.1, < 9.23.1.26
Secure Firewall Threat DefenseApplication
Affected:>= 7.0.0, < 7.0.9>= 7.1.0, < 7.2.11>= 7.4.0, < 7.4.3>= 7.6.0, < 10.0.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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 device type
    Run 'show version' on the device CLI. Look for 'Cisco Adaptive Security Appliance' or 'Cisco Firepower Threat Defense' in the output to determine if the device is ASA or FTD.
    Affected if Device is either ASA or FTD model
  2. Check the installed software version
    Run 'show version' and locate the software version number (e.g., 9.17.1, 7.2.10). Compare this version against the affected ranges: ASA: >= 9.16.1 < 9.16.4.89, >= 9.17.1 < 9.18.4.71, >= 9.20.1 < 9.20.4.19, >= 9.22.1.1 < 9.22.2.32, >= 9.23.1 < 9.23.1.26. FTD: >= 7.0.0 < 7.0.9, >= 7.1.0 < 7.2.11, >= 7.4.0 < 7.4.3, >= 7.6.0 < 10.0.0.
    Affected if Version falls within any of the listed affected ranges for your device type
  3. Verify SAML 2.0 SSO is configured
    On ASA, run 'show run webvpn' or 'show running-config webvpn' and look for 'saml idp' configuration. On FTD, run 'show running-config saml' or check via FMC under Device > VPN > SAML SSO.
    Affected if SAML SSO is enabled and configured on the device

Device is affected if it runs ASA or FTD software with a version in the affected ranges AND has SAML 2.0 SSO feature enabled.

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.9 / 7.2.11 / 7.4.3 or later
Fixed in 7.0.97.2.117.4.3
Interim mitigation

Apply the vendor-provided Cisco software patches when available. Until then, consider disabling SAML SSO if not essential, implement WAF rules to filter malicious URL parameters, and educate users about avoiding suspicious links.

Recommended fix High confidence

ASA: 9.16.4.89+, 9.18.4.71+, 9.20.4.19+, or 9.22.2.32+ | FTD: 7.0.9+, 7.2.11+, 7.4.3+, or 10.0.0+

  1. 1. Identify the current version of Cisco Secure Firewall ASA Software or Firepower Threat Defense (FTD) Software running on the device using 'show version' command
  2. 2. Determine which version branch the current installation falls into based on the affected version ranges provided
  3. 3. For ASA Software: If running 9.16.x, upgrade to 9.16.4.89 or later; if running 9.17.x or 9.18.x, upgrade to 9.18.4.71 or later; if running 9.20.x, upgrade to 9.20.4.19 or later; if running 9.22.x, upgrade to 9.22.2.32 or later
  4. 4. For FTD Software: If running 7.0.x, upgrade to 7.0.9 or later; if running 7.1.x or 7.2.x, upgrade to 7.2.11 or later; if running 7.4.x, upgrade to 7.4.3 or later; if running 7.6.x or later, upgrade to 10.0.0 or later
  5. 5. Download the appropriate Cisco software update from the Cisco Software Download center (software.cisco.com) or via your Cisco Smart Account
  6. 6. Follow standard Cisco ASA/FTD upgrade procedures: backup configuration, upload new image, perform upgrade via 'upgrade' command or ASDM/FDM
  7. 7. After upgrade, verify the new version is installed and test SAML SSO functionality to confirm the fix is working
  8. 8. Review Cisco release notes for the target version to ensure compatibility with your deployment
Caveat Standard Cisco upgrade considerations apply - review release notes for behavioral changes, ensure compatibility with other connected devices, and test in non-production environment first

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

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20102 — 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-2026-20102 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