Vulnerability in esphome-device-builder (CVE-2026-59177)
Summary
Vulnerability in esphome-device-builder (CVE-2026-59177). Risk of unauthorized operations or information disclosure. Exploitable via ingress_peer_guard. Mitigation: upgrade to 1.0.10 or later.
Original description
The description as published by the source.
Summary
On the Home Assistant add-on, the dashboard serves a trusted ingress site that skips authentication because the supervisor authenticates the request upstream. That site was binding 0.0.0.0. The add-on runs in host network mode for mDNS, so binding all interfaces also bound the host's LAN interface, and any device on the local network could reach http://:/ and get the full dashboard with no credentials.
Details
The HA add-on ingress site is intentionally unauthenticated: the supervisor's ingress proxy authenticates the browser upstream, and the dashboard's threat model assumes the site is reachable only through the supervisor's docker network. The protection depended on physically binding the site to the supervisor, but the site bound 0.0.0.0 instead. Because the add-on uses host networking, 0.0.0.0 includes the host's LAN address, so the no-auth site was reachable directly from the LAN, bypassing the supervisor and its authentication entirely.
This is an auth bypass on a boundary the dashboard explicitly defends. docs/THREAT_MODEL.md names, under the surface it still defends, "anything that lets external traffic reach the ingress site without going through the supervisor." The bug is exactly that.
The fix, in PR #1565, mirrors what the legacy add-on's nginx did:
- Bind the ingress site to loopback plus the supervisor gateway (
127.0.0.1and172.30.32.1) instead of all interfaces. Loopback serves HA core's host-network ESPHome integration, whic…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59177 has been found in esphome-device-builder.
Attackers can target a specific entry point like ingress_peer_guard over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade esphome-device-builder to 1.0.10 or later.
If unsure, ask your IT team or search "esphome-device-builder CVE-2026-59177" on the vendor's site.
CVE-2026-59177 (esphome-device-builder) — CWE-1327
Attack surface: ingress_peer_guard
Patched: 1.0.10 — apply immediately
Workaround: Upgrade to 1.0.10 or newer (an esphome container bundling device-builder 1.0.10+).
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1327) exists in esphome-device-builder. Attackers reach the vulnerable code path via ingress_peer_guard.
Check the vendor advisory for the affected versions of esphome-device-builder. Attack surface: ingress_peer_guard.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.10.
Workaround: Upgrade to 1.0.10 or newer (an esphome container bundling device-builder 1.0.10+).
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'esphome-device-builder' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'esphome-device-builder' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
esphome-device-builderを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Upgrade to 1.0.10 or newer (an esphome container bundling device-builder 1.0.10+).パッチが適用されるまでの応急処置として、Upgrade to 1.0.10 or newer (an esphome container bundling device-builder 1.0.10+). を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade esphome-device-builder to 1.0.10ステージング環境で 1.0.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com