Unauthenticated device management via dropped legacy credentials
Published Sep 14, 2026 · Updated Sep 14, 2026
Authentication bypass in ESPHome Device Builder before 1.0.12 allows remote attackers to manage devices through an exposed dashboard. DashboardSettings.parse_args drops the legacy USERNAME and PASSWORD fallback, resolves no credentials, and disables both REST and WebSocket authentication. Exposure requires an upgraded standalone deployment that retained only the legacy variables; reachable attackers can edit configurations and flash firmware.
Summary
What happened
Authentication bypass in ESPHome Device Builder before 1.0.12 allows remote attackers to manage devices through an exposed dashboard. DashboardSettings.parse_args drops the legacy USERNAME and PASSWORD fallback, resolves no credentials, and disables both REST and WebSocket authentication. Exposure requires an upgraded standalone deployment that retained only the legacy variables; reachable attackers can edit configurations and flash firmware.
The record
- CVE
- CVE-2026-59178
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- ESPHome
- Product
- ESPHome Device Builder
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo