SECUFOCUSNOW
Home›CVE index›CVE-2026-20167
Review reviewHigh

CVE-2026-20167

Cisco Cisco IoT Field Network Director (IoT-FND), iot field network director

A vulnerability in the web-based management interface of Cisco IoT Field Network Director could allow an authenticated, remote attacker with low privileges to cause a DoS condition on a remotely managed router. This vulnerability is due to improper error handling. An attacker could exploit this vulnerability by submitting crafted input to the web-based management interface. A successful exploit could allow the attacker to request unauthorized files from a remote router, causing the router to reload and resulting in a DoS condition.

CVSS
7.7
EPSS
0.27%
19.5% percentile
CISA KEV
Not listed
Published
2026.05.07
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.27%
Technical severityCVSS 7.7

Vulnerability overview

A vulnerability in the web-based management interface of Cisco IoT Field Network Director could allow an authenticated, remote attacker with low privileges to cause a DoS condition on a remotely managed router. This vulnerability is due to improper error handling. An attacker could exploit this vulnerability by submitting crafted input to the web-based management interface. A successful exploit could allow the attacker to request unauthorized files from a remote router, causing the router to reload and resulting in a DoS condition.

Affected product and versions

Product
Cisco Cisco IoT Field Network Director (IoT-FND), iot field network director
Affected versions
4.5.1, 4.4.3, 4.1.0, 4.1.3, 4.6.1, 4.1.1, 4.4.0, 4.2.0, 4.4.2, 4.3.0, 4.6.0, 4.4.4, 4.3.2, 4.1.2, 4.4.1, 4.5.0, 4.3.1, 4.7.0, 4.6.2, 4.7.1
Fixed versions
5.0.0-117

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Cisco Cisco IoT Field Network Director (IoT-FND), iot field network director and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
CWE
CWE-284