# CVE-2026-59177: ESPHome Device Builder allows unauthenticated dashboard access via the HA add-on ingress site bound to all interfaces - **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 28 Oct 2026 - **Updated:** 28 Oct 2026 - **Also known as:** GHSA-vv4j-m4vr-f3g6, PYSEC-2026-3834 ## What is CVE-2026-59177? CVE-2026-59177 is a high-severity vulnerability in esphome device-builder, published on 28 Oct 2026. ### Official description ESPHome Device Builder Dashboard is a dashboard for the ESPHome home management software. Prior to 1.0.10, the `Home Assistant` add-on's trusted `ingress` site binds to `0.0.0.0` while intentionally skipping dashboard authentication because the supervisor is expected to authenticate requests upstream. Host networking, required for mDNS, also binds this no-auth site to the `Home Assistant` host's LAN interface. Any device on that local network can therefore connect directly to the `ingress` port, bypass the supervisor, and obtain the full dashboard without credentials or operator misconfiguration. Dashboard capability includes compile-time Python execution through `external_components:`, shell execution through compile and validation subprocesses, and arbitrary access to configuration and data files, compromising the mounted `Home Assistant` configuration and managed ESPHome devices. The standalone Docker dashboard and the password-gated public port 6052 are not affected. This issue is fixed in version 1.0.10. Weakness: CWE-1327 (Binding to an Unrestricted IP Address) ## Which versions are affected by CVE-2026-59177? 3 open source packages ship an affected version, including esphome-device-builder. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `esphome-device-builder` | PyPI | All versions | 1.0.10 | | `esphome-device-builder` | PyPI | All versions | 1.0.10 | | `esphome-device-builder` | PyPI | All versions | 1.0.10 | ## How do I fix CVE-2026-59177? Upgrade esphome-device-builder to 1.0.10 or later. ## Is CVE-2026-59177 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59177 exists. Public exploit code: - ESPHome Device Builder <1.0.10 - Unauthenticated Dashboard Access (nuclei): http/cves/2026/CVE-2026-59177.yaml ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-59177 and fix it if it is affected. What it is: CVE-2026-59177 is a high-severity vulnerability in esphome device-builder, published on 28 Oct 2026. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59177 exists. Affected packages and fixed versions: - esphome-device-builder (PyPI): affected all versions; fixed in 1.0.10 - esphome-device-builder (PyPI): affected all versions; fixed in 1.0.10 - esphome-device-builder (PyPI): affected all versions; fixed in 1.0.10 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-59177/ (Markdown: https://insights.sbomify.com/CVE-2026-59177/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59177 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59177 - OSV: https://osv.dev/vulnerability/CVE-2026-59177 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-59177/ Summaries are generated and may contain mistakes; the official description above is the record.