# CVE-2026-69095: OpenWrt luci-app-bmx7 Path Traversal via bmx7-info

> Unauthenticated attackers can read sensitive files outside the intended directory via path traversal in the bmx7-info CGI script.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-4q7q-8m76-5rv8, GHSA-8qcq-jgrj-gvmj

## What is CVE-2026-69095?

CVE-2026-69095 is a high-severity path traversal vulnerability in openwrt luci, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenWrt luci-app-bmx7 before commit 5890760a454dad2cb00389dba2cdc5e779e0ffdd contains a path traversal vulnerability in the bmx7-info CGI script that allows unauthenticated attackers to read files outside the configured runtimeDir. Attackers can supply directory traversal sequences in the query string to escape the intended directory and read sensitive files accessible to the CGI process.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-69095 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69095 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69095 is a high-severity path traversal vulnerability in openwrt luci, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69095 exists.

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

## Sources

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

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