{"answers":{"affected":"3 open source packages ship an affected version, including esphome-device-builder.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59177 exists.","fix":"Upgrade esphome-device-builder to 1.0.10 or later.","what":"CVE-2026-59177 is a high-severity vulnerability in esphome device-builder, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-59177 and fix it if it is affected.\n\nWhat it is: CVE-2026-59177 is a high-severity vulnerability in esphome device-builder, published on 28 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59177 exists.\n\nAffected packages and fixed versions:\n- esphome-device-builder (PyPI): affected all versions; fixed in 1.0.10\n- esphome-device-builder (PyPI): affected all versions; fixed in 1.0.10\n- esphome-device-builder (PyPI): affected all versions; fixed in 1.0.10\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59177/ (Markdown: https://insights.sbomify.com/CVE-2026-59177/index.md)","id":"CVE-2026-59177","markdown":"https://insights.sbomify.com/CVE-2026-59177/index.md","name":"CVE-2026-59177","record":{"aliases":["GHSA-vv4j-m4vr-f3g6","PYSEC-2026-3834"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1327","name":"Binding to an Unrestricted IP Address"}],"description":"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 Python execution through `external_components:`, shell execution through compile and validation subprocesses, and arbitrary access to configuration and data files, compromising the mounted `Home Assistant` configuration and managed ESPHome devices. The standalone Docker dashboard and the password-gated public port 6052 are not affected. This issue is fixed in version 1.0.10.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-59177.yaml","stars":null,"title":"ESPHome Device Builder \u003c1.0.10 - Unauthenticated Dashboard Access"}],"tier":"weaponised"},"has_fix":true,"headline":"ESPHome Device Builder allows unauthenticated dashboard access via the HA add-on ingress site bound to all interfaces","id":"CVE-2026-59177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"ESPHome Device Builder: Renamed auth env vars silently disable dashboard authentication on upgrade","id":"CVE-2026-59178"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.10"],"introduced":["0"],"last_affected":[],"package":"esphome-device-builder","purl":null,"source":"GHSA-vv4j-m4vr-f3g6"},{"ecosystem":"PyPI","fixed":["1.0.10"],"introduced":["0"],"last_affected":[],"package":"esphome-device-builder","purl":"pkg:pypi/esphome-device-builder","source":"GHSA-vv4j-m4vr-f3g6"},{"ecosystem":"PyPI","fixed":["1.0.10"],"introduced":["0"],"last_affected":[],"package":"esphome-device-builder","purl":"pkg:pypi/esphome-device-builder","source":"PYSEC-2026-3834"}],"prev":{"headline":"Functype: MCP set_functype_version Package Alias RCE via Unsanitized pnpm install + Dynamic Import","id":"CVE-2026-59176"},"products":["device-builder"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["esphome"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-59177/"}