# CVE-2026-72841: luci-app-openvpn Path Traversal RCE via instance_name2

> Authenticated attackers can exploit path traversal in OpenWrt's OpenVPN plugin to upload malicious files and achieve persistent root code execution.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 13 Aug 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-x5wv-6f33-ph3p

## What is CVE-2026-72841?

CVE-2026-72841 is a critical path traversal vulnerability in openwrt luci, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

luci-app-openvpn fails to properly validate the instance_name2 parameter during file upload, allowing authenticated users to perform path traversal and write arbitrary files outside the intended directory. Attackers can upload malicious payloads to gain persistent root code execution by placing SSH keys in system directories accessible on reboot.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-72841 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72841 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72841 is a critical path traversal vulnerability in openwrt luci, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72841 exists.

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

## Sources

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

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