CVE-2026-18167
Stack-based buffer overflow in TP-Link Archer AX55 v4
Description
A stack-based buffer overflow vulnerability exists in the EasyMesh module of TP-Link Archer AX55 v4. When Mesh mode is enabled, a LAN attacker may submit crafted input that causes the easymesh daemon to crash and may potentially achieve remote code execution on the device. Successful exploitation may cause the EasyMesh daemon to crash and may potentially allow remote code execution when Mesh mode is enabled. This may result in high impact to the confidentiality, integrity, and availability of the affected device.
INFO
Published Date :
Sept. 3, 2026, 11:17 p.m.
Last Modified :
Sept. 3, 2026, 11:17 p.m.
Remotely Exploit :
No
Source :
f23511db-6c3e-4e32-a477-6aa17d310630
Affected Products
The following products are affected by CVE-2026-18167
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 4.0 | HIGH | f23511db-6c3e-4e32-a477-6aa17d310630 | ||||
| CVSS 4.0 | HIGH | f23511db-6c3e-4e32-a477-6aa17d310630 |
Solution
- Update TP-Link Archer AX55 v4 firmware.
- Disable Mesh mode if updating is not possible.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-18167.
| URL | Resource |
|---|---|
| https://www.tp-link.com/us/support/download/archer-ax55/v4/#Firmware | |
| https://www.tp-link.com/us/support/faq/5279/ |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-18167 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-18167
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-18167 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-18167 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by f23511db-6c3e-4e32-a477-6aa17d310630
Sep. 03, 2026
Action Type Old Value New Value Added Description A stack-based buffer overflow vulnerability exists in the EasyMesh module of TP-Link Archer AX55 v4. When Mesh mode is enabled, a LAN attacker may submit crafted input that causes the easymesh daemon to crash and may potentially achieve remote code execution on the device. Successful exploitation may cause the EasyMesh daemon to crash and may potentially allow remote code execution when Mesh mode is enabled. This may result in high impact to the confidentiality, integrity, and availability of the affected device. Added CVSS V4.0 AV:A/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Added CWE CWE-121 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/18xxx/CVE-2026-18167.json">CVE-2026-18167</a> Added Reference https://www.tp-link.com/us/support/download/archer-ax55/v4/#Firmware Added Reference https://www.tp-link.com/us/support/faq/5279/