CVE-2026-20343: Cisco Secure FMC Software Information Disclosure and Disk DoS Vulnerability

Quick Answer

CVE-2026-20343 exposes an unauthenticated FMC API that Cisco says can disclose sensitive files and exhaust disk space until the device becomes unresponsive. Preserve request and file evidence before cleanup, then apply the CVE-specific update. The vendor's disclosure wording and confidentiality score remain inconsistent.

Last verified: 2026-09-17 UTC from Cisco's advisory and CSAF record. Recheck both the affected-products and fixed-software sections before a production change.

Context

Status At A Glance

Product scope	Cisco Secure Firewall Management Center (FMC)
CVE	CVE-2026-20343
TechGeeks response tier	P1 — urgent
Publication	New final Cisco advisory
First published	2026-09-16T16:00:00+00:00
Last updated	2026-09-16T16:00:00+00:00
Cisco advisory SIR	Critical
CVE-specific Cisco SIR	High
CVSS base score / severity	7.5 — High
CVSS vector	CVSS v3.1 — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CISA KEV at last check	No — this is separate from Cisco severity and is not proof of no exploitation.
Cisco exploitation statement	The Cisco Product Security Incident Response Team (PSIRT) is not aware of any public announcements or malicious use of the vulnerabilities that are described in this advisory.

What Happened

The affected FMC API lacks authentication. Repeated calls can retrieve restricted files and consume unbounded disk space, producing denial of service when the device becomes unresponsive. Cisco tracks the defect as CSCwu36643. Its description includes disclosure, but the published 7.5 vector records C:N; this notice retains that unresolved source distinction rather than inventing a corrected score.

Affected Scope

This vulnerability affects Cisco Secure FMC Software, regardless of device configuration.

Match the exact hardware or virtual platform, installed train, patch level, enabled service, role, and management or data-plane exposure. A Cisco product-family name alone does not establish applicability.

Steps

What To Do Now

1. Confirm. Inventory Cisco Secure Firewall Management Center (FMC) and record platform, exact release, patch level, enabled feature, role, and exposure.
2. Preserve. Save UTC context plus off-device authentication, management, firewall, network, endpoint, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Scope. Compare each asset with the live Cisco advisory, including configuration prerequisites and exclusions.
4. Reduce exposure. Cisco documents no workaround for this CVE. Use only supported exposure controls while preparing the permanent fix.
5. Remediate. Confirm the affected product, release, and configuration. Cisco provides no workaround; reduce exposure where operationally feasible. Enter the exact installed product, platform, and release in Cisco Software Checker and upgrade to the returned First Fixed release. The CVE-specific live advisory and Cisco Software Checker result control the First Fixed release; any combined hardening baseline is supplemental only.
6. Validate. Confirm the resulting version, service health, logging, expected access, an expected denial, failover or cluster state, and representative dependent workflows.
7. Escalate. If evidence or exposure creates concern, open incident response and Cisco TAC recovery work rather than treating patch completion as proof of trust.

Fixed Releases And Mitigation

Investigation And Recovery

Review management authentication, account and privilege changes, API and web requests, configuration changes, crashes or restarts, resource pressure, and relevant external network telemetry for the vulnerable period. Preserve original evidence and follow Cisco TAC or incident-response guidance for containment, credential rotation, trusted rebuild, or service restoration when findings warrant it.

Notes

Exploitation Evidence

Cisco's exact status at the last check: The Cisco Product Security Incident Response Team (PSIRT) is not aware of any public announcements or malicious use of the vulnerabilities that are described in this advisory.

This CVE was not present in the TechGeeks CISA KEV snapshot at the last check. Cisco's 'not aware' statement and absence from KEV are time-bounded evidence, not claims that exploitation is impossible or has never happened. Severity and exploitation status remain separate signals.

Validation And Boundaries

This notice is documentation-backed. TechGeeks did not reproduce the exploit or independently test every fixed build. It does not prove that all members of the product family are affected, that the activity is widespread, that a clean indicator search excludes compromise, or that an update restored trust. Cisco's live advisory controls affected and fixed release information.

Related TechGeeks Resources

• TechGeeks Security Notice Center
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Cisco security advisory
• Cisco CSAF record
• Cisco September 16 publication notice
• NVD identifier record

Wrap-Up

Record whether CVE-2026-20343 applies. If it does, assign an owner and deadline appropriate to the Critical Cisco advisory SIR, preserve the evidence, complete Cisco's remediation, and document the validated result.

Correction policy: A material Cisco revision to scope, severity, exploitation status, workarounds, fixed software, or recovery guidance triggers an update and a new verification date.