Stack corruption via unchecked repeater WEP key
Published Sep 29, 2026 · Updated Sep 29, 2026
A stack-based buffer overflow in TOTOLINK N150RT firmware 3.4.0-B20201030 allows attackers to corrupt stack memory via its web interface. The /boafrm/formAjaxSet handler processes ApCliWEPKey in the setting/setWiFiRepeaterConfig branch without keeping the value within a stack buffer. TOTOLINK documents login for web management, but authentication enforcement on this route and outcomes beyond memory corruption have not been established.
Summary
What happened
A stack-based buffer overflow in TOTOLINK N150RT firmware 3.4.0-B20201030 allows attackers to corrupt stack memory via its web interface. The /boafrm/formAjaxSet handler processes ApCliWEPKey in the setting/setWiFiRepeaterConfig branch without keeping the value within a stack buffer. TOTOLINK documents login for web management, but authentication enforcement on this route and outcomes beyond memory corruption have not been established.
The record
- CVE
- CVE-2026-94953
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- TOTOLINK
- Product
- N150RT
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 29, 2026CVE publishedPublication date reported by the CVE source.
- Sep 29, 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=n/a
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started