目标达成 感谢每一位支持者 — 我们达成了 100% 目标！

目标: 1000 元 · 已筹: 1336 元

100%
请我们喝杯咖啡

CVE-2026-59178— ESPHome 设备构建器认证环境变量重命名导致认证失效

一分钟漏洞结论

影响对象
esphome device-builder
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。

ESPHome Device Builder 仪表板（Dashboard）是 ESPHome 智能家居管理软件的配套仪表板。在 1.0.12 版本之前，该仪表板从环境变量 和 读取认证凭据。而在更早的版本中，以及传统的 仪表板，读取的是简写的 和 。 当环境变量更名时，旧有的简写名称被移除且未设置回退机制。因此，那些按照旧版入门指南使用 / 来保护仪表板的运维人员在升级后会失去认证功能，导致仪表板端口对所有能访问该端口的人开放。 该问题已在 1.0.12 版本中修复。修复后的版本重新接受简写的 / 作为已弃用的回退

CVSS 9.8 · Critical
获取后续新漏洞提醒 登录后订阅

一、 漏洞 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

受影响产品

厂商 产品 影响版本 CPE 订阅
esphome device-builder < 1.0.12 -

二、漏洞 CVE-2026-59178 的公开POC

# POC 描述 源链接 神龙链接
AI 生成 POC 高级

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2026-59178 的情报信息

请登录查看更多情报信息。

CVE-2026-59178 其他参考 (4)

IV. Related Vulnerabilities

Same vendor: esphome
Same weakness: CWE-306

V. Comments for CVE-2026-59178

暂无评论

发表评论