ESPHome through 2026.7.0-dev contains an operator-precedence bug in the cv.url validator in esphome/config_validation.py. Because binds tighter than , any file: URI passes validation regardless of netloc. This validator gates the field of the external_components YAML directive's git source schema, which is passed to (git supports file:// natively).
CVE-2026-71259
Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 8.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(high)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity86% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
August 5, 2026
Last Modified
August 10, 2026
Advisory Details (2)
Auto-updated Aug 5, 2026esphome/esphome/config_validation.py at dev · esphome/esphome · GitHub
https://github.com/esphome/esphome/blob/dev/esphome/config_validation.pyGitHub - esphome/esphome: ESPHome is a system to control your ESP32, ESP8266, BK72xx, RP2040 by simple yet powerful configuration files and control them remotely through Home Automation systems. · GitHub
https://github.com/esphome/esphomeVendor Advisories for CVE-2026-71259(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 30× in last 7d / 69× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 02:19 UTCEG score recompute
- 2026-08-21 02:19 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 14:20 UTCGHSA enrichment
- 2026-08-20 00:54 UTCEG score recompute
- 2026-08-20 00:54 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 12:50 UTCGHSA enrichment
- 2026-08-19 00:51 UTCEG score recompute
- 2026-08-19 00:51 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 12:49 UTCGHSA enrichment
- 2026-08-18 00:15 UTCEG score recompute
- 2026-08-18 00:15 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 12:07 UTCGHSA enrichment
- 2026-08-17 00:09 UTCEG score recompute
- 2026-08-17 00:09 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:10 UTCEG score recompute
- 2026-08-16 12:10 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-16 00:12 UTCGHSA enrichment
Show 44 moreShow fewer
- 2026-08-15 12:13 UTCEG score recompute
- 2026-08-15 12:13 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-15 00:14 UTCGHSA enrichment
- 2026-08-14 12:15 UTCGHSA enrichment
- 2026-08-14 00:17 UTCEG score recompute
- 2026-08-14 00:17 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 12:18 UTCGHSA enrichment
- 2026-08-13 00:19 UTCEG score recompute
- 2026-08-13 00:19 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 12:21 UTCGHSA enrichment
- 2026-08-12 00:22 UTCGHSA enrichment
- 2026-08-11 12:21 UTCGHSA enrichment
- 2026-08-11 00:23 UTCEG score recompute
- 2026-08-11 00:23 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 12:24 UTCEG score recompute
- 2026-08-10 12:24 UTCGHSA enrichment
- 2026-08-10 12:02 UTCGHSA enrichment
- 2026-08-10 11:22 UTCEG score recompute
- 2026-08-10 11:22 UTCGHSA enrichment
- 2026-08-10 04:17 UTCGHSA enrichment
- 2026-08-09 16:18 UTCGHSA enrichment
- 2026-08-09 04:20 UTCEG score recompute
- 2026-08-09 04:20 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 16:22 UTCGHSA enrichment
- 2026-08-08 04:23 UTCEG score recompute
- 2026-08-08 04:23 UTCGHSA enrichment
- 2026-08-07 16:24 UTCGHSA enrichment
- 2026-08-07 04:26 UTCGHSA enrichment
- 2026-08-06 16:27 UTCEG score recompute
- 2026-08-06 16:27 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 04:29 UTCGHSA enrichment
- 2026-08-05 16:30 UTCEG score recompute
- 2026-08-05 16:30 UTCGHSA enrichment
- 2026-08-05 16:13 UTCEG score recompute
- 2026-08-05 16:13 UTCGHSA enrichment
- 2026-08-05 13:28 UTCEG score recompute
- 2026-08-05 13:08 UTCEG score recompute
- 2026-08-05 13:07 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-71259?
When was CVE-2026-71259 disclosed?
Is CVE-2026-71259 actively exploited?
What is the CVSS score of CVE-2026-71259?
How do I remediate CVE-2026-71259?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71259
Is Your Infrastructure Affected by CVE-2026-71259?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.