CVE-2025-25305
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 15% of all known CVEs.
References
Related Vulnerabilities
Other CWE-940 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-61932 | Critical | 9.8 | 2.6% | KEV | - |
| CVE-2024-32388 | Medium | 5.3 | 1.2% | - | Fix |
| CVE-2025-23018 | Medium | 5.4 | 1.0% | - | - |
| CVE-2023-48387 | High | 8.8 | 1.0% | - | - |
| CVE-2023-3663 | High | 8.8 | 1.0% | - | Fix |
| CVE-2025-23019 | Medium | 5.4 | 1.0% | - | - |
Common questions
How do I fix CVE-2025-25305?
No published fix for CVE-2025-25305 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2025-25305 being actively exploited?
Not that we know of. CVE-2025-25305 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.24% is the estimated probability that it will be exploited in the next 30 days. That is higher than 15% of all scored CVEs.
How severe is CVE-2025-25305?
CVE-2025-25305 has a CVSS v3 base score of 7.0, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2025-25305
Markdown
[](https://tridentstack.com/cve/CVE-2025-25305)HTML
<a href="https://tridentstack.com/cve/CVE-2025-25305"><img src="https://tridentstack.com/cve/badge/CVE-2025-25305.svg" alt="CVE-2025-25305"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-02-18.