Authenticated service crash via unvalidated flash-write input
Published Aug 7, 2026 · Updated Aug 7, 2026
Improper input validation in TP-Link Archer A6 v4 before V4_1.15.10 Build 260625 Rel.25447 allows remote authenticated users to crash httpd. The HTTP-WRITEOEM handler passes insufficiently validated user-supplied data to internal flash-write handling logic. High-privilege authentication and an adjacent network position are required; exploitation crashes httpd or the device and removes web-interface access.
Summary
What happened
Improper input validation in TP-Link Archer A6 v4 before V4_1.15.10 Build 260625 Rel.25447 allows remote authenticated users to crash httpd. The HTTP-WRITEOEM handler passes insufficiently validated user-supplied data to internal flash-write handling logic. High-privilege authentication and an adjacent network position are required; exploitation crashes httpd or the device and removes web-interface access.
The record
- CVE
- CVE-2026-9031
- Published
- Aug 7, 2026
- Updated
- Aug 7, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- Archer A6
- Classifications
- CWE-20, CAPEC-153, T1499.004
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 7, 2026CVE publishedPublication date reported by the CVE source.
- Aug 7, 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=0 <V4_1.15.10 Build 260625 Rel.25447
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo