CVE-2025-25305
Home Assistant Core is an open source home automation that puts …
Home Assistant Core is an open source home automation that puts local control and privacy first. Affected versions are subject to a potential man-in-the-middle attacks due to missing SSL certificate verification in the project codebase and used third-party libraries. In the past, `aiohttp-session`/`request` had the parameter `verify_ssl` to control SSL certificate verification. This was a boolean value. In `aiohttp` 3.0, this parameter was deprecated in favor of the `ssl` parameter. Only when `ssl` is set to `None` or provided with a correct configured SSL context the standard SSL certificate verification will happen. When migrating integrations in Home Assistant and libraries used by Home Assistant, in some cases the `verify_ssl` parameter value was just moved to the new `ssl` parameter. This resulted in these integrations and 3rd party libraries using `request.ssl = True`, which unintentionally turned off SSL certificate verification and opened up a man-in-the-middle attack vector. This issue has been addressed in version 2024.1.6 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/home-assistant/core/security/advisories/GHSA-m3pm-rpgg-5wj6
- github.com/home-assistant/core/commit/8c6547f1b64f4a3d9f10090b97383353c9367892
- nvd.nist.gov/vuln/detail/CVE-2025-25305
- github.com/advisories/GHSA-m3pm-rpgg-5wj6
- nvd.nist.gov/vuln/detail/CVE-2025-25305
- cve.org/CVERecord?id=CVE-2025-25305
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.