Vulnerability in esphome-device-builder (CVE-2026-59178)
Summary
Vulnerability in esphome-device-builder (CVE-2026-59178). Successful exploitation can lead to full system takeover. Exploitable via esphome. Mitigation: upgrade to 1.0.12 or later.
Original description
The description as published by the source.
Summary
The dashboard reads its authentication credentials from $ESPHOME_USERNAME and $ESPHOME_PASSWORD. Earlier versions, and the legacy esphome dashboard, read the bare $USERNAME and $PASSWORD instead. When the env vars were renamed the bare names were dropped with no fallback, so an operator who had protected their dashboard with USERNAME / PASSWORD (as the older getting started guide documented) loses authentication on upgrade and the dashboard starts open to anyone who can reach its port.
Details
Credentials are resolved in DashboardSettings.parse_args. The fallback originally read os.getenv("USERNAME") and os.getenv("PASSWORD"). The env var rename (#265) replaced those with ESPHOME_USERNAME / ESPHOME_PASSWORD and intentionally removed the bare names, because $USERNAME collides with the OS login user on Linux and Windows and reading it on its own would silently promote the shell user to the dashboard username.
The rename closed that footgun but introduced a backward compatibility break: a deployment that set only the bare names now resolves to no credentials, using_password is false, and the REST auth middleware and the WebSocket login gate are both disabled. The process logs a WITHOUT AUTHENTICATION banner at startup, but a container started detached (docker run -d) never surfaces it, so the exposure is silent in practice.
This reaches users because the dashboard subcommand of the ghcr.io/esphome/esphome container runs this…
Source: NIST National Vulnerability Database 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-59178 has been found in esphome-device-builder.
Attackers can target a specific entry point like esphome over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade esphome-device-builder to 1.0.12 or later.
If unsure, ask your IT team or search "esphome-device-builder CVE-2026-59178" on the vendor's site.
CVE-2026-59178 (esphome-device-builder) — CWE-306 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: esphome / USERNAME / PASSWORD / DashboardSettings.parse_args
Patched: 1.0.12 — apply immediately
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-306) exists in esphome-device-builder. Attackers reach the vulnerable code path via esphome without authentication.
Check the vendor advisory for the affected versions of esphome-device-builder. Attack surface: esphome / USERNAME / PASSWORD / DashboardSettings.parse_args.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 1.0.12.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade esphome-device-builder to 1.0.12ステージング環境で 1.0.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web github.com