Adjacent-network HTTP service crash via crafted requests
Published Mar 5, 2026 · Updated Mar 5, 2026
Improper input validation in TP-Link EAP610 v3 firmware before 1.6.0 allows remote attackers on an adjacent network to crash its HTTP service. The HTTP service accepts crafted requests without adequate input validation, but TP-Link has not disclosed the affected request field, handler, or failing operation. Reachability requires adjacent network access; a successful request interrupts the management service until the access point is rebooted.
Summary
What happened
Improper input validation in TP-Link EAP610 v3 firmware before 1.6.0 allows remote attackers on an adjacent network to crash its HTTP service. The HTTP service accepts crafted requests without adequate input validation, but TP-Link has not disclosed the affected request field, handler, or failing operation. Reachability requires adjacent network access; a successful request interrupts the management service until the access point is rebooted.
The record
- CVE
- CVE-2025-7375
- Published
- Mar 5, 2026
- Updated
- Mar 5, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- EAP610
- Classifications
- CWE-20, CAPEC-6, T1499
- Attack vector
- adjacent
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 5, 2026CVE publishedPublication date reported by the CVE source.
- Mar 5, 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.6.0
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