# CVE-2026-67352: luci-app-https-dns-proxy Stored XSS via resolver_url

> Authenticated users can inject JavaScript via the resolver_url parameter, leading to XSS when administrators view the status page.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-8ggv-vmgf-36wq

## What is CVE-2026-67352?

CVE-2026-67352 is a medium-severity cross-site scripting vulnerability in openwrt luci, published on 1 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

luci-app-https-dns-proxy contains a stored cross-site scripting vulnerability in the resolver_url parameter that allows authenticated users to inject active HTML. When an administrator views the HTTPS DNS Proxy status page, the resolver URL is rendered as raw HTML and executes JavaScript in the administrator's browser origin.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-67352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67352 is a medium-severity cross-site scripting vulnerability in openwrt luci, published on 1 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67352 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-67352/ (Markdown: https://insights.sbomify.com/CVE-2026-67352/index.md)
```

## Sources

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

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