CVE-2026-59178— ESPHome Device Builder Dashboard 授权问题漏洞
一分钟漏洞结论
影响对象
esphome device-builder
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
ESPHome Device Builder Dashboard是ESPHome组织开源的一个智能家居设备固件构建工具。 ESPHome Device Builder Dashboard 1.0.12之前版本存在授权问题漏洞，该漏洞源于仪表盘身份验证凭据的环境变量重命名后未保留旧变量回退，导致原先使用USERNAME和PASSWORD保护的实例在升级后失去身份验证，任何可访问其端口的攻击者均可未经授权访问。
影响版本矩阵 1
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| esphome | device-builder | < 1.0.12 |
affected |
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-59178 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
ESPHome Device Builder: Renamed auth env vars silently disable dashboard authentication on upgrade
来源: CVE Program / CVE List V5
Vulnerability 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.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
关键功能的认证机制缺失
来源: CVE Program / CVE List V5
Vulnerability Title
ESPHome Device Builder Dashboard 授权问题漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
ESPHome Device Builder Dashboard是ESPHome组织开源的一个智能家居设备固件构建工具。 ESPHome Device Builder Dashboard 1.0.12之前版本存在授权问题漏洞，该漏洞源于仪表盘身份验证凭据的环境变量重命名后未保留旧变量回退，导致原先使用USERNAME和PASSWORD保护的实例在升级后失去身份验证，任何可访问其端口的攻击者均可未经授权访问。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| esphome | device-builder | < 1.0.12 | - |
|
二、漏洞 CVE-2026-59178 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-59178 的情报信息
请登录查看更多情报信息。
CVE-2026-59178 补丁与修复 (2)
CVE-2026-59178 厂商安全公告 (1)
CVE-2026-59178 厂商页面 (1)
-
🔗 Release 1.0.12 · esphome/device-builder · GitHub x_refsource_MISC
IV. Related Vulnerabilities
Same product: device-builder