luci-app-lxc contains an ACL inconsistency vulnerability that allows low-privileged authenticated...
Summary
Vulnerability reported (CVE-2026-72842). Successful exploitation can lead to full system takeover. Exploitable via lxc_name.
Original description
The description as published by the source.
luci-app-lxc contains an ACL inconsistency vulnerability that allows low-privileged authenticated LuCI users to access backend container management routes without proper authorization checks. Attackers can exploit path traversal via /.%2E in the lxc_name parameter to escape container directories and control host-side scripts executed through lxc.hook.start-host, achieving root code execution on the OpenWrt host.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-72842 has been found.
Attackers can target a specific entry point like lxc_name over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-72842" on the vendor's site.
CVE-2026-72842 — CWE-73 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: lxc_name
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-73) has been reported. Attackers reach the vulnerable code path via lxc_name.
Check the vendor advisory for the affected versions. Attack surface: lxc_name.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com