CVE-2026-59178Patch

LOWCVSS 9.8 · CRITICAL

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

ESPHome Device Builder Dashboard is a dashboard for the ESPHome home management software. Prior to version 1.0.12, 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. The issue is fixed in 1.0.12. The bare `$USERNAME` / `$PASSWORD` are accepted again as a deprecated fallback so previously protected instances stay protected across the upgrade without operator intervention, with a loud deprecation warning at startup directing operators to rename them to `$ESPHOME_USERNAME` / `$ESPHOME_PASSWORD`. The fallback is gated on `$PASSWORD` being set and is only adopted as a pair, so the OS provided `$USERNAME` is never read on its own and the original collision footgun stays closed. A lone bare `$PASSWORD` with no username still fails loud as a credential mismatch rather than starting unauthenticated. This restores compatibility rather than failing closed on the legacy names, because the priority is that an instance which was protected before the upgrade stays protected without the operator having to act; the deprecation warning plus a future removal handles the migration. Operators should migrate to the `$ESPHOME_*` names. The esphome container delivers the fix in the 2026.6.2 release, which bumps its pinned `esphome-device-builder` version to 1.0.12. Without upgrading, restore authentication immediately by setting the new env vars to the same values, on any affected version. Alternatively, do not expose the dashboard port to untrusted networks, and check the startup logs for the `WITHOUT AUTHENTICATION` banner to confirm whether a given instance is currently open.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-306

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 2 signals
  • Technical details provided in 1 signal
  • Peaked 1d ago at 1 mentions (2026-09-14); latest day: 1
  • 2 total mentions across 2 days

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-09-14: 1Mentions · 2026-09-16: 1Patch / Workaround · 2026-09-14: 1Patch / Workaround · 2026-09-16: 1Technical Details · 2026-09-14: 109-1409-16
Signal classification1 categories
Patch
2100.0%
Referenced assets2 URLs
Full discourse2 posts
  • Cybersecurity News DE@cybsecuritynews
    Patch

    #schwachstellen ESPHome Dashboard offen nach Upgrade: Kritische Schwachstelle CVE-2026-59178 behoben #cve202659178 #esphome #esphomedevicebuilderdashboard #esphomedevicebuilder https://cybersecurity-news.de/esphome-dashboard-cve-2026-59178

    Post summary

    The text announces the resolution of CVE-2026-59178 in ESPHome Dashboard following an upgrade, confirming a critical vulnerability was fixed. The primary focus is on the availability of a patch rather than exploitation or technical details.

    0000034
    12 followersView on X
  • CVE@CVEnew
    Patch

    CVE-2026-59178 ESPHome Device Builder Dashboard is a dashboard for the ESPHome home management software. Prior to version 1.0.12, the dashboard reads its authentication credentials … https://www.cve.org/CVERecord?id=CVE-2026-59178

    Post summary

    CVE-2026-59178 describes a vulnerability in ESPHome's Device Builder Dashboard prior to version 1.0.12, where authentication credentials are improperly handled. The text emphasizes remediation via an upgrade to version 1.0.12.

    00000728
    58.1K followersView on X

Explore more