CVE-2025-25305 json
SSL validation for outgoing requests in Home Assistant Core and used libs not correct
published 2025-02-18 20 mo ago modified 2026-07-07 4 mo ago also EUVD-2025-4771 , GHSA-m3pm-rpgg-5wj6 , PYSEC-2026-1452
- cvss
- 7.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi homeassistant 2024.1.6
- home-assistant home-assistant 2024.1.6
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 20 mo ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L |
| GitHub | 3.1 | 7.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L |
| OSV | 3.1 | 7.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | homeassistant | <2024.1.6 |
2024.1.6 |
Affected products
- home-assistant core
Classification
References
-
github.com
/home-assistant/core/commit/8c6547f1b64f4a3d9f10090b97383353c9367892
web
-
github.com
/home-assistant/core/security/advisories/GHSA-m3pm-rpgg-5wj6
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-25305
advisory
-
github.com
/home-assistant/core
package
-
pypi.org
/project/homeassistant
package
-
github.com
/advisories/GHSA-m3pm-rpgg-5wj6
advisory
Sources
- CVE List CVE-2025-25305
- GitHub Advisory GHSA-m3pm-rpgg-5wj6
- NVD CVE-2025-25305
- OSV PYSEC-2026-1452
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.