Root command execution via parental-control parameters
Published Aug 24, 2026 · Updated Aug 25, 2026
OS command injection in TP-Link Archer BE800 V1, BE3600 V1, and AX75 V1 allows remote attackers on the LAN to execute root commands. The parental control functionality fails to filter and neutralize shell metacharacters in certain parameters before OS command execution; parameter names remain undisclosed. No authentication is required, but the attacker must reach the router from its LAN; exploitation permits complete device and network-traffic compromise.
Summary
What happened
OS command injection in TP-Link Archer BE800 V1, BE3600 V1, and AX75 V1 allows remote attackers on the LAN to execute root commands. The parental control functionality fails to filter and neutralize shell metacharacters in certain parameters before OS command execution; parameter names remain undisclosed. No authentication is required, but the attacker must reach the router from its LAN; exploitation permits complete device and network-traffic compromise.
The record
- CVE
- CVE-2026-9254
- Published
- Aug 24, 2026
- Updated
- Aug 25, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- Archer AX75
- Classifications
- CWE-78, CAPEC-248, T1059
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 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 <1.1.6 Build 260716
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