This vulnerability in OpenWrt's LuCI web interface achieves root persistence through a path traversal flaw in the instance_name2 parameter of the luci-app-openvpn configuration upload handler. Because LuCI runs as root on OpenWrt devices, any authenticated file-write primitive collapses the privilege boundary entirely—unlike a properly sandboxed web application where a file upload bug might be limited to the web server's user context. The attacker writes SSH keys to system directories, achieving persistence that survives device reboots and firmware upgrades due to OpenWrt's overlay filesystem behavior. This is not a one-off coding error; this is the second documented instance of this exact pattern in OpenWrt-related components (CVE-2019-15126 in Webmin exhibited the same secondary-parameter validation collapse), confirming a recurring vulnerability class where upload handlers accumulate new parameters over time without uniform validation propagation. Check whether luci-app-openvpn is actually needed in your deployment—WireGuard has largely superseded OpenVPN in forward-looking OpenWrt installations, and unused authenticated interfaces should be removed rather than audited. Assume default LuCI credentials exist on a significant fraction of deployed devices and audit for this explicitly. Implement file integrity monitoring on /etc/dropbear/ and /etc/authorized_keys/—the persistence mechanism targets these paths and will survive your next scheduled reboot, which many OpenWrt devices perform automatically. The CVSS 9.9 rating accurately captures severity but understates the operational reality: disclosure and patch availability are meaningless when the vulnerable population persists for quarters due to OpenWrt's manual update model and the compounding debt of overlay-persisted modifications that survive upgrades.
CVE-2026-72841
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedluci-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA detailed technical summary for this CVE is being prepared.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $5,750. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-72841 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis vulnerability in OpenWrt's LuCI web interface achieves root persistence through a path traversal flaw in the `instance_name2` parameter of the luci-app-openvpn configuration upload handler. Because LuCI runs as root on OpenWrt devices, any authenticated file-write primitive collapses the privilege boundary entirely—unlike a properly sandboxed web application where a file upload bug might be limited to the web server's user context. The attacker writes SSH keys to system directories, achieving persistence that survives device reboots and firmware upgrades due to OpenWrt's overlay filesystem behavior. This is not a one-off coding error; this is the second documented instance of this exact pattern in OpenWrt-related components (CVE-2019-15126 in Webmin exhibited the same secondary-parameter validation collapse), confirming a recurring vulnerability class where upload handlers accumulate new parameters over time without uniform validation propagation. Check whether luci-app-openvpn is actually needed in your deployment—WireGuard has largely superseded OpenVPN in forward-looking OpenWrt installations, and unused authenticated interfaces should be removed rather than audited. Assume default LuCI credentials exist on a significant fraction of deployed devices and audit for this explicitly. Implement file integrity monitoring on /etc/dropbear/ and /etc/authorized_keys/—the persistence mechanism targets these paths and will survive your next scheduled reboot, which many OpenWrt devices perform automatically. The CVSS 9.9 rating accurately captures severity but understates the operational reality: disclosure and patch availability are meaningless when the vulnerable population persists for quarters due to OpenWrt's manual update model and the compounding debt of overlay-persisted modifications that survive upgrades.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-72841 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data