Authenticated root code execution via LXC path traversal
Published Aug 13, 2026 · Updated Aug 14, 2026
Authorization bypass in OpenWrt LuCI 25.12.2 allows remote authenticated users to execute code as root through luci-app-lxc. The backend concatenates an unvalidated lxc_name into a container configuration path, so /.%2E traversal writes a host script invoked by lxc.hook.start-host. A low-privileged LuCI session can reach ACL-unprotected admin/services/lxc routes and compromise the OpenWrt host.
Summary
What happened
Authorization bypass in OpenWrt LuCI 25.12.2 allows remote authenticated users to execute code as root through luci-app-lxc. The backend concatenates an unvalidated lxc_name into a container configuration path, so /.%2E traversal writes a host script invoked by lxc.hook.start-host. A low-privileged LuCI session can reach ACL-unprotected admin/services/lxc routes and compromise the OpenWrt host.
The record
- CVE
- CVE-2026-72842
- Published
- Aug 13, 2026
- Updated
- Aug 14, 2026
- Vendor
- OpenWrt
- Product
- LuCI
- Classifications
- T1059.004, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- OpenWrt luci-app-lxc ACL inconsistency to host root reportfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo