Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY23 SECURITY RECORDS

home-assistant

core

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at core, but registry activity is not a publisher support boundary.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-91129 22 Sep 2026 core: < 2026.2.3 2026.2.3. Update reference ↗
CVE-2026-91130 22 Sep 2026 core: < 2026.7.0 2026.7.0. Update reference ↗
CVE-2026-66061 7 Aug 2026 < 2026.5.0 2026.5.0. Update reference ↗
CVE-2026-66060 7 Aug 2026 < 2026.5.3 2026.8.1. Update reference ↗
CVE-2026-59717 7 Aug 2026 < 2026.6.1 2026.6.1. Update reference ↗
CVE-2026-55844 29 Jun 2026 < 2025.5.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-54318 23 Jun 2026 < 2026.5.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-54317 23 Jun 2026 < 2026.6.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44698 29 May 2026 < 2026.4.4; < 2026.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-33045 27 Mar 2026 >= 2025.02, < 2026.01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-33044 27 Mar 2026 >= 2020.02, < 2026.01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-62172 14 Oct 2025 >= 2025.1.0, < 2025.10.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-25305 18 Feb 2025 < 2024.1.6 2024.1.6 Update reference ↗
CVE-2023-50715 15 Dec 2023 < 2023.12.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-41893 19 Oct 2023 < 2023.9.0 2023.9.0 Update reference ↗
CVE-2023-41894 19 Oct 2023 < 2023.9.0 2023.9.0 Update reference ↗
CVE-2023-41895 19 Oct 2023 < 2023.9.0 2023.9.0 Update reference ↗
CVE-2023-41896 19 Oct 2023 Home Assistant Core : < 2023.8.0; home-assistant-js-websocket: < 8.2.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41897 19 Oct 2023 < 2023.9.0 2023.9.0 Update reference ↗
CVE-2023-41899 19 Oct 2023 < 2023.9.0 2023.9.0 Update reference ↗
CVE-2023-41898 19 Oct 2023 < 2023.9.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-44385 19 Oct 2023 < 2023.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-27482 8 Mar 2023 < 2023.3.2; < 2023.03.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.