Unauthenticated memory corruption via oversized KeyStr
Published May 31, 2026 · Updated May 31, 2026
Stack-based buffer overflow in TOTOLINK N300RH 6.1c.1353_B20190305 allows remote attackers to corrupt memory through its web interface. Handling an oversized KeyStr value in wireless.so setWiFiBasicConfig overwrites the function's stack buffer. No authentication or user interaction is required; the public proof of concept establishes remote reachability, not reliable code execution.
Summary
What happened
Stack-based buffer overflow in TOTOLINK N300RH 6.1c.1353_B20190305 allows remote attackers to corrupt memory through its web interface. Handling an oversized KeyStr value in wireless.so setWiFiBasicConfig overwrites the function's stack buffer. No authentication or user interaction is required; the public proof of concept establishes remote reachability, not reliable code execution.
The record
- CVE
- CVE-2026-10187
- Published
- May 31, 2026
- Updated
- May 31, 2026
- Vendor
- TOTOLINK
- Product
- N300RH Firmware
- Classifications
- CWE-119, CWE-121, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 31, 2026CVE publishedPublication date reported by the CVE source.
- May 31, 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=6.1c.1353_B20190305
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
- CNA-linked KeyStr proof of conceptproof of concept · unverified
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