Authenticated code execution via unbounded device-name formatting
Published Feb 8, 2026 · Updated Feb 8, 2026
Stack-based buffer overflow in Tenda RX3 16.03.13.11 allows remote authenticated users to execute code via a crafted devName parameter. The set_device_name function passes devName to sprintf for a 256-byte stack buffer without checking its length. Low-privilege access to the network management endpoint is required; an oversized value corrupts the return address and can crash httpd or execute code.
Summary
What happened
Stack-based buffer overflow in Tenda RX3 16.03.13.11 allows remote authenticated users to execute code via a crafted devName parameter. The set_device_name function passes devName to sprintf for a 256-byte stack buffer without checking its length. Low-privilege access to the network management endpoint is required; an oversized value corrupts the return address and can crash httpd or execute code.
The record
- CVE
- CVE-2026-2185
- Published
- Feb 8, 2026
- Updated
- Feb 8, 2026
- Vendor
- Shenzhen Tenda Technology Co., Ltd.
- Product
- RX3
- Classifications
- CWE-121, CWE-119, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 8, 2026CVE publishedPublication date reported by the CVE source.
- Feb 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16.03.13.11
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- RX3 setBlackRule Python proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo