p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de esphome-device-builder

Vulnérabilité publiée pour esphome-device-builder au cours des 30 derniers jours : 1. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 2

  1. CVE-2026-59177

    Élevée · CVSS 8.8EPSS 1,17%Code d’exploitation publicCorrectif disponible

    ESPHome Device Builder allows unauthenticated dashboard access via the HA add-on ingress site bound to all interfaces

    ESPHome Device Builder Dashboard is a dashboard for the ESPHome home management software. Prior to 1.0.10, the `Home Assistant` add-on's trusted `ingress` site binds to `0.0.0.0` while intentionally skipping dashboard authentication because the supervisor is expected to authenticate requests upstream. Host networking, required for mDNS, also binds this no-auth site to the `Home Assistant` host's LAN interface. Any device on that local network can therefore connect directly to the `ingress` port, bypass the supervisor, and obtain the full dashboard without credentials or operator misconfiguration. Dashboard capability includes compile-time Pyt

    • Mettez à jour vers 1.0.10
    Publication Mise à jour
  2. CVE-2026-59178

    Critique · CVSS 9.8EPSS 0,78%Correctif disponible

    ESPHome Device Builder: Renamed auth env vars silently disable dashboard authentication on upgrade

    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.

    • Mettez à jour vers 1.0.12
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →