# CVE-2026-5511: Information Disclosure via Diagnostic Interface Due to Improper Input Validation on TP-Link's Archer AX72

> An authenticated admin can view diagnostic command syntax via improper input validation in the web interface, exposing limited usage information.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2026
- **Updated:** 19 May 2026
- **Also known as:** GHSA-wcm6-86h3-r2cq

## What is CVE-2026-5511?

CVE-2026-5511 is a medium-severity vulnerability in TP-Link Systems Inc. Archer AX72 (SG) v1.0, published on 19 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the web management interface of Archer AX72 (SG) v1, the network diagnostic feature improperly handles invalid user input, resulting in limited exposure of diagnostic command usage information. 

An authenticated attacker with administrative privileges could exploit this issue to confirm the presence of the diagnostic utility and view its valid command-line syntax and options.  The exposed information is limited in scope and does not include sensitive system data.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2026-5511?

It affects 1 product.


Products: Tp-Link Archer Ax72 Firmware.

## How do I fix CVE-2026-5511?

No fix has been published for CVE-2026-5511 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5511 being exploited?

There is no known exploitation of CVE-2026-5511 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5511 and fix it if it is affected.

What it is: CVE-2026-5511 is a medium-severity vulnerability in TP-Link Systems Inc. Archer AX72 (SG) v1.0, published on 19 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5511 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Archer AX72 (SG) v1.0. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5511/ (Markdown: https://insights.sbomify.com/CVE-2026-5511/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5511
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5511
- OSV: https://osv.dev/vulnerability/CVE-2026-5511

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5511/
Summaries are generated and may contain mistakes; the official description above is the record.