# CVE-2026-15271: TOTOLINK EX200 Web boa.conf least privilege violation

> Remote attackers can exploit a least privilege violation in the web interface configuration to escalate privileges on affected TOTOLINK routers.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-f8vj-vmgj-67x6

## What is CVE-2026-15271?

CVE-2026-15271 is a high-severity vulnerability in TOTOLINK A3000RU, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in TOTOLINK A3000RU, A3100R, A950RG, AC1200T10, CP450, CS185R_T10 and EX200 up to 20260906. Affected by this issue is some unknown functionality of the file /etc/boa/boa.conf of the component Web Interface. The manipulation leads to least privilege violation. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitation is known to be difficult.

Weakness: CWE-272 (Least Privilege Violation), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-15271 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15271 is a high-severity vulnerability in TOTOLINK A3000RU, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15271 in the wild and no public exploit code.

Affected product: TOTOLINK A3000RU. 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-15271/ (Markdown: https://insights.sbomify.com/CVE-2026-15271/index.md)
```

## Sources

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

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