Advisory record · GHSA-rrxg-g2pf-6hh4

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

CVSS 9.8 CriticalCriticalEPSS 0.0078 · 56th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 14 Sept 2026, 18:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
esphome-device-builderPyPI<1.0.121.0.12
Identifiers
GHSA-rrxg-g2pf-6hh4 · CVE-2026-59178 · PYSEC-2026-4049
Weakness (CWE)
CWE-306
Published
14 Sept 2026
Updated
1 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The esphome-device-builder package before 1.0.12 drops dashboard authentication when operators upgrade and had set the older bare USERNAME and PASSWORD environment variables, which were renamed to ESPHOME_USERNAME and ESPHOME_PASSWORD without a fallback. An unauthenticated client with network access to the dashboard port can then manage devices, including editing configurations and flashing firmware. Upgrade to 1.0.12, which accepts the bare names again as a deprecated fallback; until then, set the ESPHOME_USERNAME and ESPHOME_PASSWORD variables to the same values.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0078, the 56th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:09 UTC First seen by agentprime
  2. 31 Oct 2026, 14:09 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.