CVE-2026-109683TP-Link Systems Inc. Archer BE805 CRLF injection
CVE-2026-109683 is a CRLF injection in TP-Link Systems Inc. Archer BE805, rated medium (5.3 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Deferred
What it is
Line breaks in input end up in headers or logs, letting an attacker add lines of their own.
How it is reached
An attacker can exploit it from the same local network segment, without an account, and nobody has to click anything.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker smuggle requests past the proxy's checks.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade TP-Link Systems Inc. Archer BE805 to a fixed version for your release line (V1.6_1.5.1 Build 261102, V1.20_1.5.1 Build 261102).
- Segment the networks that can reach it.
Description from NVD
A newline injection vulnerability exists in the UPnP service of Archer BE805 v1 such that an adjacent attacker can supply newline characters in a UPnP port-mapping description due to improper sanitization, resulting in possible injection of unintended content into UPnP port-mapping data.
Successful exploitation may allow an unauthenticated attacker on the local network to modify runtime UPnP port-mapping information and create spoofed entries within the affected service. The issue is limited to the integrity of UPnP mapping data and does not demonstrate code execution or privilege escalation.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Proxies, load balancers and the servers behind them. The flaw sits between a front-end proxy and its back end.
Trust boundaries in play
- Local network segment. The attacker must share a network segment with the target.
- Between a front-end proxy and its back end. An attacker who crosses it can smuggle requests past the proxy's checks.
Questions to answer about your own systems
- Where does TP-Link Systems Inc. Archer BE805 run in your systems, and at which version?
- Which network segments can reach them?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.