CVSS 3.1
8.8 highCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HHigh (8.8) in esphome device-builder. EPSS 1.2% estimated probability of exploitation activity in the next 30 days. Fixed in esphome-device-builder 1.0.10.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hesphome-device-builder (PyPI): fixed in 1.0.10Explain CVE-2026-59177 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-59177?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-59177?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-59177 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| esphome device-builder | < 1.0.10 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-vv4j-m4vr-f3g6 | PyPI | esphome-device-builder | <1.0.10 | 1.0.10 |
| PYSEC-2026-3834 | PyPI | esphome-device-builder | <1.0.10 | 1.0.10 |
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.