VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

homeassistant: vulnerability history, versions and safety

homeassistant is a package in the PyPI ecosystem. Vulert records 24 vulnerabilities for it across 78 releases, from Sep 2019 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
24 vulnerabilities recorded C2 H4 M4 L2 U12
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
17 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all homeassistant vulnerabilities

Vulert verdict on homeassistant 2026.10.2 i

Updated on 23 Oct 2026

Good news: 2026.10.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 24.

Package health score 64/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

What to do: Stay on 2026.10.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 2026.10.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2026.10.2 — unaffected i
  • Vulnerabilities on record 24 over 7 years · 17 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 0 i
  • Depended on by 7 packages i
  • Stars 91,649 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for homeassistant, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2026.10.2 16 Oct 2026 none Apache-2.0 — Details →
2026.10.1 10 Oct 2026 none Apache-2.0 — Details →
2026.10.0 07 Oct 2026 none Apache-2.0 — Details →
2026.10.0b7 07 Oct 2026 none Apache-2.0 — Details →
2026.10.0b6 07 Oct 2026 none Apache-2.0 — Details →
2026.10.0b5 07 Oct 2026 none Apache-2.0 — Details →
2026.10.0b4 07 Oct 2026 none Apache-2.0 — Details →
2026.10.0b3 06 Oct 2026 none Apache-2.0 — Details →
2026.10.0b2 06 Oct 2026 none Apache-2.0 — Details →
2026.10.0b1 05 Oct 2026 none Apache-2.0 — Details →
2026.10.0b0 30 Sep 2026 none Apache-2.0 — Details →
2026.9.4 27 Sep 2026 none Apache-2.0 — Details →
2026.9.3 18 Sep 2026 none Apache-2.0 — Details →
2026.9.2 11 Sep 2026 none Apache-2.0 — Details →
2026.9.1 05 Sep 2026 none Apache-2.0 — Details →
2026.9.0 02 Sep 2026 none Apache-2.0 — Details →
2026.9.0b9 02 Sep 2026 none Apache-2.0 — Details →
2026.9.0b8 02 Sep 2026 none Apache-2.0 — Details →
2026.9.0b7 02 Sep 2026 none Apache-2.0 — Details →
2026.9.0b6 01 Sep 2026 none Apache-2.0 — Details →
2026.9.0b5 31 Aug 2026 none Apache-2.0 — Details →
2026.9.0b4 29 Aug 2026 none Apache-2.0 — Details →
2026.9.0b3 29 Aug 2026 none Apache-2.0 — Details →
2026.9.0b2 28 Aug 2026 none Apache-2.0 — Details →
2026.9.0b1 27 Aug 2026 none Apache-2.0 — Details →
2026.9.0b0 26 Aug 2026 none Apache-2.0 — Details →
2026.8.3 21 Aug 2026 none Apache-2.0 — Details →
2026.8.2 14 Aug 2026 none Apache-2.0 — Details →
2026.8.1 07 Aug 2026 none Apache-2.0 — Details →
2026.8.0 05 Aug 2026 none Apache-2.0 — Details →
2026.8.0b6 05 Aug 2026 none Apache-2.0 — Details →
2026.8.0b5 04 Aug 2026 none Apache-2.0 — Details →
2026.8.0b4 03 Aug 2026 none Apache-2.0 — Details →
2026.8.0b3 31 Jul 2026 none Apache-2.0 — Details →
2026.8.0b2 30 Jul 2026 none Apache-2.0 — Details →
2026.8.0b1 30 Jul 2026 none Apache-2.0 — Details →
2026.8.0b0 29 Jul 2026 none Apache-2.0 — Details →
2026.7.4 24 Jul 2026 none Apache-2.0 — Details →
2026.7.3 21 Jul 2026 none Apache-2.0 — Details →
2026.7.2 10 Jul 2026 none Apache-2.0 — Details →
2026.7.1 03 Jul 2026 none Apache-2.0 — Details →
2026.7.0 01 Jul 2026 none Apache-2.0 — Details →
2026.7.0b4 01 Jul 2026 C1 U1 Apache-2.0 Yes Details →
2026.7.0b3 30 Jun 2026 C1 U1 Apache-2.0 Yes Details →
2026.7.0b2 27 Jun 2026 C1 U1 Apache-2.0 Yes Details →
2026.7.0b1 24 Jun 2026 C1 U1 Apache-2.0 Yes Details →
2026.7.0b0 24 Jun 2026 C1 U1 Apache-2.0 Yes Details →
2026.6.4 19 Jun 2026 C1 U1 Apache-2.0 Yes Details →
2026.6.3 12 Jun 2026 C1 U1 Apache-2.0 Yes Details →
2026.6.2 09 Jun 2026 C1 U1 Apache-2.0 Yes Details →
2026.6.1 05 Jun 2026 C1 U1 Apache-2.0 Yes Details →
2026.6.0 03 Jun 2026 C1 U1 Apache-2.0 Yes Details →
2026.6.0b4 03 Jun 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.6.0b3 03 Jun 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.6.0b2 01 Jun 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.6.0b1 01 Jun 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.6.0b0 27 May 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.5.4 22 May 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.5.3 19 May 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.5.2 15 May 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.5.1 08 May 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.5.0 06 May 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.5.0b4 06 May 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.5.0b3 06 May 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.5.0b2 05 May 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.5.0b1 04 May 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.5.0b0 29 Apr 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.4 24 Apr 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.3 17 Apr 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.2 11 Apr 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.1 03 Apr 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.0 01 Apr 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.0b10 01 Apr 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.0b9 01 Apr 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.0b8 31 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.0b7 31 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.0b5 30 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.0b4 27 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.0b3 26 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.0b2 26 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.0b1 26 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.4.0b0 25 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.3.4 24 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.3.3 20 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.3.2 16 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.3.1 06 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.3.0 04 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.3.0b4 04 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.3.0b3 04 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.3.0b2 02 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.3.0b1 26 Feb 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.3.0b0 25 Feb 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.2.3 20 Feb 2026 C2 H1 U3 Apache-2.0 Yes Details →
2026.2.2 13 Feb 2026 C2 H1 M1 U4 Apache-2.0 Yes Details →
2026.2.1 06 Feb 2026 C2 H1 M1 U4 Apache-2.0 Yes Details →
2026.2.0 04 Feb 2026 C2 H1 M1 U4 Apache-2.0 Yes Details →
2026.2.0b5 04 Feb 2026 C2 H1 M1 U4 Apache-2.0 Yes Details →
2026.2.0b4 04 Feb 2026 C2 H1 M1 U4 Apache-2.0 Yes Details →
2026.2.0b3 03 Feb 2026 C2 H1 M1 U4 Apache-2.0 Yes Details →
2026.2.0b2 02 Feb 2026 C2 H1 M1 U4 Apache-2.0 Yes Details →
2026.2.0b1 30 Jan 2026 C2 H1 M1 U4 — Yes Details →
2026.2.0b0 28 Jan 2026 C2 H1 M1 U4 — Yes Details →
2026.1.3 23 Jan 2026 C2 H1 M1 U4 — Yes Details →
2026.1.2 16 Jan 2026 C2 H1 M1 U4 — Yes Details →
2026.1.1 12 Jan 2026 C2 H1 M1 U4 — Yes Details →
2026.1.0 07 Jan 2026 C2 H1 M1 U4 — Yes Details →
2026.1.0b5 07 Jan 2026 C2 H1 M1 L2 U6 — Yes Details →
2026.1.0b4 06 Jan 2026 C2 H1 M1 L2 U6 — Yes Details →
2026.1.0b3 05 Jan 2026 C2 H1 M1 L2 U6 — Yes Details →
2026.1.0b2 31 Dec 2025 C2 H1 M1 L2 U6 — Yes Details →
2026.1.0b1 30 Dec 2025 C2 H1 M1 L2 U6 — Yes Details →
2026.1.0b0 29 Dec 2025 C2 H1 M1 L2 U6 — Yes Details →
2025.12.5 29 Dec 2025 C2 H1 M1 L2 U6 — Yes Details →
2025.12.4 19 Dec 2025 C2 H1 M1 L2 U6 — Yes Details →
2025.12.3 12 Dec 2025 C2 H1 M1 L2 U6 — Yes Details →
2025.12.2 08 Dec 2025 C2 H1 M1 L2 U6 — Yes Details →
2025.12.1 05 Dec 2025 C2 H1 M1 L2 U6 — Yes Details →
2025.12.0 03 Dec 2025 C2 H1 M1 L2 U6 — Yes Details →
2025.12.0b9 03 Dec 2025 C2 H1 M1 L2 U6 — Yes Details →
2025.12.0b8 03 Dec 2025 C2 H1 M1 L2 U6 — Yes Details →

The newest 120 of 1,634 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2022 1
  • 2023 3
  • 2025 3
  • 2026 16

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 17 of the 24 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for homeassistant

The 5 most severe of 24 vulnerabilities recorded for this package

Search all 24 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-64825: Home Assistant Core Path Traversal Vulnerability via Backup Upload 9.3 critical 2026.6.0 21 Jul 2026
CVE-2026-91130: Home Assistant XSS Vulnerability in Statistics Graph Card 9.3 critical 2026.7.0 01 Oct 2026
CVE-2026-91130: Home Assistant XSS Vulnerability in Statistics Graph Card 9.3 critical 2026.7.0 22 Sep 2026
CVE-2026-64825: Home Assistant Core Path Traversal Vulnerability via Backup Upload 9.3 critical 2026.6.0 19 Aug 2026
CVE-2025-62172: Home Assistant Stored XSS Vulnerability in Energy Dashboard 8.5 high 2025.10.2 07 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About homeassistant

Is homeassistant safe to use?

Vulert records 24 vulnerabilities for homeassistant in PyPI: 2 critical, 4 high, 4 medium and 2 low, plus 12 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is homeassistant's Vulert package health score?

Vulert scores homeassistant 64/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of homeassistant affected?

No. 2026.10.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of homeassistant should I use?

2026.10.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does homeassistant have?

24 vulnerabilities are recorded for homeassistant in the PyPI ecosystem: 2 critical, 4 high, 4 medium and 2 low, plus 12 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new homeassistant vulnerabilities disclosed?

17 vulnerabilities were recorded for homeassistant in the last 12 months, and the oldest entry in this database dates to 23 Sep 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of homeassistant are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor homeassistant for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the homeassistant version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.