Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

ESPHome Device Builder Dashboard: Unauthenticated dashboard access via the HA add-on ingress site bound to all interfaces

CVE-2026-59177GHSA-vv4j-m4vr-f3g6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (esphome-device-builder 1.0.10), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-59177: 1.17% estimated exploitation activity in the next 30 days; percentile 67.41 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary On the Home Assistant add-on, the dashboard serves a trusted ingress site that skips authentication because the supervisor authenticates the request upstream. That site was binding 0.0.0.0. The add-on runs in host network mode for mDNS, so binding all interfaces also bound the host's LAN interface, and any device on the local network could reach http://<ha-ip:<ingressport/ and get the full dashboard with no credentials. Details The HA add-on ingress site is intentionally unauthenticated: the supervisor's ingress proxy authenticates the browser upstream, and the dashboard's threat model assumes the site is reachable only through the supervisor's docker network. The protection depended on physically binding the site to the supervisor, but the site bound 0.0.0.0 instead. Because the add-on uses host networking, 0.0.0.0 includes the host's LAN address, so the no-auth site was reachable directly from the LAN, bypassing the supervisor and its authentication entirely. This is an…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-vv4j-m4vr-f3g6

  2. Revision 2 · amended ·

    Amended from osv record GHSA-vv4j-m4vr-f3g6

  3. Revision 1 · created ·

    Published from ghsa record GHSA-vv4j-m4vr-f3g6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-59177

Advisory: ESPHome Device Builder Dashboard: Unauthenticated dashboard access via the HA add-on ingress site bound to all interfaces
IDs: CVE-2026-59177, GHSA-vv4j-m4vr-f3g6
Record: https://patchnext.com/advisories/cve-2026-59177 (revision 3, source checked 26 Oct 2026, 13:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: esphome-device-builder 1.0.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI esphome-device-builder: affected < 1.0.10; fixed in 1.0.10

## Suggested inspection (read-only)
- `python -m pip show esphome-device-builder`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on esphome-device-builder.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vv4j-m4vr-f3g6 (GitHub-reviewed advisory GHSA-vv4j-m4vr-f3g6 lists affected ranges: PyPI esphome-device-builder >=0 <1.0.10)
- Verified: https://osv.dev/vulnerability/GHSA-vv4j-m4vr-f3g6 (OSV record GHSA-vv4j-m4vr-f3g6 lists affected ranges: PyPI esphome-device-builder >=0 <1.0.10 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…