CVE-2026-20101
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 · uneditedA vulnerability in the SAML 2.0 single sign-on (SSO) feature of Cisco Secure Firewall ASA Software and Secure FTD Software could allow an unauthenticated, remote attacker to cause the device to reload unexpectedly, resulting in a DoS condition. This vulnerability is due to insufficient error checking when processing SAML messages. An attacker could exploit this vulnerability by sending crafted SAML messages to the SAML service. A successful exploit could allow the attacker to cause the device to reload, resulting in a DoS condition.
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 · moderate confidenceThis vulnerability exists in the SAML 2.0 single sign-on feature of Cisco Secure Firewall ASA and FTD software. It is caused by insufficient error checking when processing SAML messages, allowing an unauthenticated remote attacker to send crafted SAML messages that trigger an unexpected device reload, resulting in denial of service.
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>= 9.12.1, < 9.16.4.85>= 9.17.1, < 9.18.4.66>= 9.19.1, < 9.20.4>= 9.22.1.1, < 9.22.2.4>= 9.23.1, < 9.23.1.7>= 6.4.0, < 7.0.9>= 7.1.0, < 7.2.11>= 7.3.0, < 7.4.3>= 7.6.0, < 7.6.4>= 7.7.0, < 7.7.11CVSS 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
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Cisco product and software versionRun 'show version' on the device CLI to display the running software and version numberAffected if The version falls within any of the listed affected ranges for ASA Software or FTD Software
-
Determine if SAML SSO is enabledRun 'show run saml' or 'show running-config saml' to inspect the SAML configurationAffected if SAML configuration exists and the SAML service is active on the device
-
Verify the SAML identity provider (IdP) configurationRun 'show saml idp' to list configured identity providers and their metadata settingsAffected if One or more IdP entries are configured, indicating SAML SSO is in use
-
Confirm device management interface exposureReview the device's access lists and interface security levels to determine if the management interface (or the interface where SAML listens) is reachable from untrusted networksAffected if The interface on which the SAML service listens accepts external connections from untrusted networks
The device is affected if it runs any ASA Software or FTD Software version within the listed ranges AND has SAML SSO configured and accessible from the network where the attacker can send malicious SAML messages.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.0.97.2.117.4.3
Apply the vendor-provided security update or patch for CVE-2026-20101 when available. If immediate patching is not possible, consider restricting SAML service access to trusted sources via access lists or VPN tunnels.
ASA: upgrade to 9.16.4.85+, 9.18.4.66+, 9.20.4+, or 9.22.2.4+ | FTD: upgrade to 7.0.9+, 7.2.11+, 7.4.3+, or 7.6.4+
- 1. Identify the current Cisco ASA or FTD software version using 'show version' command
- 2. Determine the appropriate upgrade path based on current version per the affected version ranges
- 3. Download the fixed software release from Cisco (refer to sec.cloudapps.cisco.com for official downloads)
- 4. Back up the current device configuration
- 5. Upload the new software image to the device
- 6. Follow Cisco upgrade procedures to install the new software version
- 7. Verify the device reloads successfully and SAML SSO functionality operates normally
- 8. Confirm the new version is running using 'show version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20101 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-20101 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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