UPnP Newline Injection Vulnerability in TP-Link Archer BE805
- Exploited
- No known exploitation
- Fix
- Fixed in V1.6_1.5.1 Build 261102, V1.20_1.5.1 Build 261102
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: V1.6_1.5.1 Build 261102, V1.20_1.5.1 Build 261102.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 5/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The UPnP service in the TP-Link Archer BE805 router has a newline injection flaw in how it handles port-mapping descriptions. An attacker on the same local network, without logging in, can insert extra content into UPnP port-mapping data and create spoofed entries, though the issue does not allow code execution or privilege escalation.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: V1.6_1.5.1 Build 261102, V1.20_1.5.1 Build 261102.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- TP-Link Systems Inc. Archer BE805 v1
fixed in V1.6_1.5.1 Build 261102; fixed in V1.20_1.5.1 Build 261102
Evidence 3
- Advisory
- Patch
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-109683
Is CVE-2026-109683 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-109683?
Archer BE805 v1: before V1.6_1.5.1 Build 261102; before V1.20_1.5.1 Build 261102.Source: cve.now feed data
How do I fix CVE-2026-109683?
Upgrade to a fixed version: V1.6_1.5.1 Build 261102, V1.20_1.5.1 Build 261102.Source: cve.now feed data