Docker-Proxy hubcmdui - Missing Authentication on /api/config
Docker-Proxy through 5.1.9 exposes the hubcmdui configuration endpoint /api/config without authentication. An unauthenticated remote attacker can read the full server configuration, including the WeChat/Telegram monitoring webhook URLs and bot token inside monitoringConfig, the menuItems structure and docker host settings, and can overwrite configuration via the unauthenticated POST handler. The fix restricts anonymous callers to a public subset (theme, language, logo, proxyDomain). References: https://github.com/dqzboy/Docker-Proxy/security/advisories/GHSA-xxpq-v3jg-w39m https://github.com/dqzboy/Docker-Proxy/commit/a173befc5d163b1206b40298871153026fee9474 https://github.com/dqzboy/Docker-Proxy/issues/109 https://www.vulncheck.com/advisories/docker-proxy-through-5.1.9-missing-authentication-via-hubcmdui-api-config https://nvd.nist.gov/vuln/detail/CVE-2026-116070 Remediation: Upgrade Docker-Proxy to a release after 5.1.9 that restricts anonymous /api/config access to a public subset (theme, language, logo, proxyDomain).
Used 20 times · 10 assets checked · domain, subdomain, ipv4