Authentication bypass via prefix-length credential comparison
Published Sep 2, 2025 · Updated Sep 2, 2025
Authentication bypass in ESPHome 2025.8.0 on ESP-IDF allows remote attackers to access web_server functions over the local network. AsyncWebServerRequest::authenticate compares only the client value's length against the Base64-encoded user:password digest, so an empty value or matching prefix passes. No credentials or user interaction are required; exposed functions include protected content and OTA firmware updates when OTA is enabled.
Summary
What happened
Authentication bypass in ESPHome 2025.8.0 on ESP-IDF allows remote attackers to access web_server functions over the local network. AsyncWebServerRequest::authenticate compares only the client value's length against the Base64-encoded user:password digest, so an empty value or matching prefix passes. No credentials or user interaction are required; exposed functions include protected content and OTA firmware updates when OTA is enabled.
The record
- CVE
- CVE-2025-57808
- Published
- Sep 2, 2025
- Updated
- Sep 2, 2025
- Vendor
- ESPHome
- Product
- ESPHome
- Classifications
- CWE-303, T1190
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2025CVE publishedPublication date reported by the CVE source.
- Sep 2, 2025Record 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== 2025.8.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.
Weakness, pattern, technique
Public exploit references
- Empty Basic Authorization header proof of conceptproof of concept · demonstrated
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