# CVE-2025-25305

## Summary

- **CVE ID:** CVE-2025-25305
- **Severity:** HIGH
- **CVSS Score:** 7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L)
- **CWE:** CWE-940
- **Published:** Feb 18, 2025
- **Last Modified:** Mar 12, 2026

## Description

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.

## Affected Products

- home-assistant — core (< 2024.1.6)

## References

- [CNA](https://github.com/home-assistant/core/security/advisories/GHSA-m3pm-rpgg-5wj6)

## Exploitation Prediction (EPSS)

- **EPSS Score:** 0.25%
- **EPSS Percentile:** 15.8

---
_Exported from OnDuty AI Vulnerability Intelligence on 2026-09-10._