Code execution via file URI validation bypass
Published Aug 5, 2026 · Updated Aug 5, 2026
Code execution in ESPHome through 2026.7.0 allows local users to run Python through a crafted external_components URL. The cv.url validator in config_validation.py accepts every file URI because its scheme check is combined with a file-scheme exception using incorrect operator precedence. Processing attacker-supplied YAML must be induced; the accepted local repository is cloned and loaded into Python's import path, executing its component code.
Summary
What happened
Code execution in ESPHome through 2026.7.0 allows local users to run Python through a crafted external_components URL. The cv.url validator in config_validation.py accepts every file URI because its scheme check is combined with a file-scheme exception using incorrect operator precedence. Processing attacker-supplied YAML must be induced; the accepted local repository is cloned and loaded into Python's import path, executing its component code.
The record
- CVE
- CVE-2026-71259
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- ESPHome
- Product
- ESPHome
- Classifications
- CWE-184, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2026.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo