CVE
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.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. luci-app-travelmate is installed on the device. Affects the master, openwrt-25.12, openwrt-24.10 and openwrt-23.05 branches of luci-app-travelmate.
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.
Original 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.
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.
“with luci-app-travelmate installed that configure delegated/read-only LuCI/ rpcd accounts”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
luci-app-travelmate is installed on the device. Affects the master, openwrt-25.12, openwrt-24.10 and openwrt-23.05 branches of luci-app-travelmate.Workaround: 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.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- openwrt luci
Version range not reported
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · openwrt/luci · Advisory GHSA-66wf-c49f-5whc |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130751 |
| Record | NVD · CVE-2026-130751 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130751
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: cve.now feed data
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: github.com
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: github.com
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: github.com
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: github.com