# CVE-2026-130752: OpenWrt LuCI luci-app-uhttpd before d38658b Filesystem-Wide File Read via ACL


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-4h7q-j9hv-2536, GHSA-hjjj-g65r-fwmf

## What is CVE-2026-130752?

CVE-2026-130752 is a medium-severity vulnerability in openwrt luci, published on 18 Nov 2026. 

### Official description

OpenWrt LuCI luci-app-uhttpd before commit d38658bedbdd811b798da16b49301478c6cf21af grants '/*' file read in its rpcd read ACL, which rpcd's fnmatch matching applies to every path. Users delegated only luci-app-uhttpd read access can read any file as root, including /etc/shadow, /etc/config/* credentials, /etc/uhttpd.key, and /etc/dropbear keys.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2026-130752 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130752 is a medium-severity vulnerability in openwrt luci, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130752 in the wild and no public exploit code.

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-130752/ (Markdown: https://insights.sbomify.com/CVE-2026-130752/index.md)
```

## Sources

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

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