Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2025-57808 is a high-severity Incorrect Implementation of Authentication Algorithm (CWE-303) vulnerability in Esphome Esphome Firmware. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique External Remote Services (T1133); ranked in the top 27% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
ESPHome version 2025.8.0 on the ESP-IDF platform contains an authentication bypass in its web_server component. The check incorrectly accepts an empty base64-encoded Authorization header value or any value that is a substring of the correct credential, granting access to all web_server endpoints without knowledge of the configured username or password.
An attacker on the adjacent network can reach the affected device and invoke any web_server functionality, including over-the-air firmware updates when that feature is enabled. The flaw requires no prior credentials and no user interaction, resulting in high impact to confidentiality and integrity.
The project has released version 2025.8.1 to correct the authentication logic. The accompanying GitHub security advisory GHSA-mxh2-ccgj-8635 and the referenced commit detail the patch and recommend immediate upgrade for any deployment still running 2025.8.0.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-26385
Vulnerability Data
ESPHome is a system to control microcontrollers remotely through Home Automation systems. In version 2025.8.0 in the ESP-IDF platform, ESPHome's web_server authentication check can pass incorrectly when the client-supplied base64-encoded Authorization value is empty or is a substring of the…
more
correct value. This allows access to web_server functionality (including OTA, if enabled) without knowing any information about the correct username or password. This issue has been patched in version 2025.8.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation at post-design stages directly uncovers incorrect implementations of required authentication algorithms.
Requiring documented development processes, standards, and tools reduces the chance that an established authentication algorithm is coded incorrectly.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require correct implementation of authentication algorithms.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure authentication control directly requires correct implementation of authentication algorithms.
Security testing can detect flawed authentication implementations but does not prevent them by itself.
Cryptography control addresses proper use of authentication algorithms but is broader than authentication alone.
Secure development lifecycle includes verification steps that can catch incorrect authentication implementations.
Application security requirements can specify correct authentication algorithm use but do not guarantee correct implementation.
Secure coding practices reduce the likelihood of incorrect authentication algorithm implementation.