# CVE-2026-20169: Cisco IoT Field Network Director Command Injection Vulnerability

> Authenticated attackers can execute commands and manipulate files on remote routers via the Cisco IoT Field Network Director web interface.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2026
- **Updated:** 6 May 2026
- **Also known as:** GHSA-rx82-7g7m-r755

## What is CVE-2026-20169?

CVE-2026-20169 is a medium-severity command injection vulnerability in Cisco IoT Field Network Director (IoT-FND), published on 6 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco IoT Field Network Director could allow an authenticated, remote attacker with low privileges to access files and execute commands on a remote router.

This vulnerability is due to insufficient input validation of user-supplied data. An attacker could exploit this vulnerability by submitting crafted input in the web-based management interface. A successful exploit could allow the attacker to create, read, or delete files and execute limited commands in user EXEC mode on a remote router.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-20169?

It affects 1 product.


Products: Cisco Iot Field Network Director.

## How do I fix CVE-2026-20169?

No fix has been published for CVE-2026-20169 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-20169 being exploited?

There is no known exploitation of CVE-2026-20169 in the wild and no public exploit code.

Public exploit code:

- https://github.com/gigachadusers/CVE-2026-20169 (github_poc): https://github.com/gigachadusers/CVE-2026-20169

## Other vulnerabilities in Cisco IoT Field Network Director (IoT-FND)

- [CVE-2020-3531](https://insights.sbomify.com/CVE-2020-3531/): Cisco IoT Field Network Director Unauthenticated REST API Vulnerability (critical 9.8)
- [CVE-2018-0270](https://insights.sbomify.com/CVE-2018-0270/): Cross-site request forgery in Cisco IoT Field Network Director (high 8.8)
- [CVE-2020-26072](https://insights.sbomify.com/CVE-2020-26072/): Cisco IoT Field Network Director SOAP API Authorization Bypass Vulnerability (high 8.7)
- [CVE-2026-20167](https://insights.sbomify.com/CVE-2026-20167/): Cisco IoT Field Network Director Remote Device Denial of Service Vulnerability (high 7.7)
- [CVE-2020-3392](https://insights.sbomify.com/CVE-2020-3392/): Cisco IoT Field Network Director Missing API Authentication Vulnerability (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-20169 and fix it if it is affected.

What it is: CVE-2026-20169 is a medium-severity command injection vulnerability in Cisco IoT Field Network Director (IoT-FND), published on 6 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-20169 in the wild and no public exploit code.

Affected product: Cisco IoT Field Network Director (IoT-FND). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-20169/ (Markdown: https://insights.sbomify.com/CVE-2026-20169/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-20169
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-20169
- OSV: https://osv.dev/vulnerability/CVE-2026-20169

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-20169/
Summaries are generated and may contain mistakes; the official description above is the record.