# CVE-2026-116070: Docker-Proxy through 5.1.9 Missing Authentication via hubcmdui /api/config


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-xxpq-v3jg-w39m

## What is CVE-2026-116070?

CVE-2026-116070 is a medium-severity vulnerability in dqzboy Docker-Proxy, published on 25 Oct 2026. 

### Official description

Docker-Proxy through 5.1.9 contains a missing authentication vulnerability in the hubcmdui routes/config.js that allows unauthenticated attackers to read and overwrite configuration via /api/config. Attackers can retrieve the WeChat webhook URL and Telegram bot token, and overwrite menuItems links, proxyDomain, and the monitoring webhook destination receiving alerts.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-116070 being exploited?

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

Public exploit code:

- Docker-Proxy hubcmdui - Missing Authentication on /api/config (nuclei): http/cves/2026/CVE-2026-116070.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116070 is a medium-severity vulnerability in dqzboy Docker-Proxy, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116070 exists.

Affected product: dqzboy Docker-Proxy. 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-116070/ (Markdown: https://insights.sbomify.com/CVE-2026-116070/index.md)
```

## Sources

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

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