CVE Tools

CVE-2026-20343

Cisco Secure Firewall Management Center Software Information Disclosure and Disk Denial of Service Vulnerability

No known exploitation. EPSS puts it in the 52nd percentile. No fix published yet.

Check it yourself

OpenVAS · 1 check

e.g. OID 1.3.6.1.4.1.25623.1.0.157957

Run the check

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

  • Cisco Secure Firewall Management CenterAffected: 7.3.0Upgrade to: not statedAffected: 7.3.1Upgrade to: not statedAffected: 7.3.1.1Upgrade to: not statedAffected: 7.4.0Upgrade to: not stated + 27 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether your organization runs Cisco Secure Firewall Management Center (FMC), especially any internet-reachable management interface.
  2. Ask your Cisco support contact or IT provider whether your FMC version is affected by CVE-2026-20343; no fixed version has been published in the available information.
  3. Restrict access to FMC management interfaces to trusted administrator networks and block public internet access.
  4. Watch FMC disk-space and availability alerts for unusual rapid storage consumption, then contact Cisco support if activity is found.

What it is

From the CVE record

A vulnerability in a critical API for Cisco Secure FMC Software could allow an unauthenticated, remote attacker to download sensitive files and use unbounded disk space. This vulnerability exists because a critical API lacks authentication. An attacker could exploit this vulnerability by repeatedly invoking the API. A successful exploit could allow the attacker to download sensitive files that should be restricted and consume disk space so the device could become unresponsive, causing a DoS condition.

In plain language

Written by AI from the record

Cisco Secure Firewall Management Center (FMC) has a serious flaw that can expose restricted files and make the system stop responding; businesses using it should act now.

Unauthenticated remote access to a critical FMC API allows sensitive-file disclosure and disk exhaustion through repeated requests, causing denial of service.

If you're affected

  • Restricted file exposure
  • Firewall management outage
  • Network administration disruption
  • Recovery and cleanup costs

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS52nd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.7% chance of exploitation activity in the next 30 days, which ranks it in the 52nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 36 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Record updated
  3. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

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

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Cisco, not every advisory.