VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

esphome: vulnerability history, versions and safety

esphome is a package in the PyPI ecosystem. Vulert records 12 vulnerabilities for it across 120 releases, from Sep 2021 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded H4 M2 U6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
6 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all esphome vulnerabilities

Vulert verdict on esphome 2026.10.0 i

Updated on 23 Oct 2026

Action needed: 2026.10.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 78/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 2026.10.0 — affected i
  • Vulnerabilities on record 12 over 4 years · 6 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Stars 11,934 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT 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 esphome, 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.0 21 Oct 2026 U1 MIT Yes Details →
2026.10.0b6 21 Oct 2026 U1 MIT Yes Details →
2026.10.0b5 19 Oct 2026 U1 MIT Yes Details →
2026.10.0b4 13 Oct 2026 U1 MIT Yes Details →
2026.10.0b3 12 Oct 2026 U1 MIT Yes Details →
2026.10.0b2 09 Oct 2026 U1 MIT Yes Details →
2026.10.0b1 07 Oct 2026 U1 MIT Yes Details →
2026.9.1 29 Sep 2026 U1 MIT Yes Details →
2026.9.0 16 Sep 2026 U1 MIT Yes Details →
2026.9.0b5 16 Sep 2026 U1 MIT Yes Details →
2026.9.0b4 14 Sep 2026 U1 MIT Yes Details →
2026.9.0b3 09 Sep 2026 U1 MIT Yes Details →
2026.9.0b2 07 Sep 2026 U1 MIT Yes Details →
2026.9.0b1 03 Sep 2026 U1 MIT Yes Details →
2026.8.2 31 Aug 2026 U1 MIT Yes Details →
2026.8.1 23 Aug 2026 U1 MIT Yes Details →
2026.8.0 20 Aug 2026 U1 MIT Yes Details →
2026.8.0b6 19 Aug 2026 U1 MIT Yes Details →
2026.8.0b5 18 Aug 2026 U1 MIT Yes Details →
2026.8.0b4 16 Aug 2026 U1 MIT Yes Details →
2026.8.0b3 14 Aug 2026 U1 MIT Yes Details →
2026.8.0b2 13 Aug 2026 U1 MIT Yes Details →
2026.8.0b1 12 Aug 2026 U1 MIT Yes Details →
2026.7.4 05 Aug 2026 U1 MIT Yes Details →
2026.7.3 28 Jul 2026 U1 MIT Yes Details →
2026.7.2 23 Jul 2026 U1 MIT Yes Details →
2026.7.1 20 Jul 2026 U1 MIT Yes Details →
2026.7.0 16 Jul 2026 U1 MIT Yes Details →
2026.7.0b4 15 Jul 2026 U1 MIT Yes Details →
2026.7.0b3 14 Jul 2026 U1 MIT Yes Details →
2026.7.0b2 13 Jul 2026 U1 MIT Yes Details →
2026.7.0b1 09 Jul 2026 U1 MIT Yes Details →
2026.6.5 09 Jul 2026 U1 MIT Yes Details →
2026.6.4 01 Jul 2026 U1 MIT Yes Details →
2026.6.3 29 Jun 2026 U1 MIT Yes Details →
2026.6.2 20 Jun 2026 U1 MIT Yes Details →
2026.6.1 18 Jun 2026 U1 MIT Yes Details →
2026.6.0 18 Jun 2026 U1 MIT Yes Details →
2026.6.0b4 17 Jun 2026 U1 MIT Yes Details →
2026.6.0b3 16 Jun 2026 U1 MIT Yes Details →
2026.6.0b2 15 Jun 2026 U1 MIT Yes Details →
2026.6.0b1 11 Jun 2026 U1 MIT Yes Details →
2026.5.3 05 Jun 2026 U1 MIT Yes Details →
2026.5.2 02 Jun 2026 U1 MIT Yes Details →
2026.5.1 24 May 2026 U1 MIT Yes Details →
2026.5.0 21 May 2026 U1 MIT Yes Details →
2026.5.0b4 20 May 2026 U1 MIT Yes Details →
2026.5.0b3 20 May 2026 U1 MIT Yes Details →
2026.5.0b2 18 May 2026 U1 MIT Yes Details →
2026.5.0b1 14 May 2026 U1 MIT Yes Details →
2026.4.5 06 May 2026 U1 MIT Yes Details →
2026.4.4 05 May 2026 U1 MIT Yes Details →
2026.4.3 28 Apr 2026 U1 MIT Yes Details →
2026.4.2 23 Apr 2026 U1 MIT Yes Details →
2026.4.1 20 Apr 2026 U1 MIT Yes Details →
2026.4.0 15 Apr 2026 U1 MIT Yes Details →
2026.4.0b3 15 Apr 2026 U1 MIT Yes Details →
2026.4.0b2 13 Apr 2026 U1 MIT Yes Details →
2026.4.0b1 09 Apr 2026 U1 MIT Yes Details →
2026.3.3 07 Apr 2026 U1 MIT Yes Details →
2026.3.2 01 Apr 2026 U1 MIT Yes Details →
2026.3.1 23 Mar 2026 U1 MIT Yes Details →
2026.3.0 19 Mar 2026 U1 MIT Yes Details →
2026.3.0b5 18 Mar 2026 U1 MIT Yes Details →
2026.3.0b4 18 Mar 2026 U1 MIT Yes Details →
2026.3.0b3 17 Mar 2026 U1 MIT Yes Details →
2026.3.0b2 15 Mar 2026 U1 MIT Yes Details →
2026.3.0b1 11 Mar 2026 U1 MIT Yes Details →
2026.2.4 03 Mar 2026 U1 MIT Yes Details →
2026.2.3 02 Mar 2026 U1 MIT Yes Details →
2026.2.2 26 Feb 2026 U1 MIT Yes Details →
2026.2.1 20 Feb 2026 U1 MIT Yes Details →
2026.2.0 18 Feb 2026 U1 MIT Yes Details →
2026.2.0b5 18 Feb 2026 U1 MIT Yes Details →
2026.2.0b4 18 Feb 2026 U1 MIT Yes Details →
2026.2.0b3 17 Feb 2026 U1 MIT Yes Details →
2026.2.0b2 14 Feb 2026 U1 MIT Yes Details →
2026.2.0b1 12 Feb 2026 U1 MIT Yes Details →
2026.1.5 10 Feb 2026 U1 MIT Yes Details →
2026.1.4 04 Feb 2026 U1 MIT Yes Details →
2026.1.3 30 Jan 2026 U1 MIT Yes Details →
2026.1.2 25 Jan 2026 U1 MIT Yes Details →
2026.1.1 22 Jan 2026 U1 MIT Yes Details →
2026.1.0 21 Jan 2026 U1 MIT Yes Details →
2026.1.0b4 20 Jan 2026 U1 MIT Yes Details →
2026.1.0b3 17 Jan 2026 U1 MIT Yes Details →
2025.12.7 17 Jan 2026 U1 MIT Yes Details →
2026.1.0b2 15 Jan 2026 U1 MIT Yes Details →
2026.1.0b1 14 Jan 2026 U1 MIT Yes Details →
2025.12.6 13 Jan 2026 M1 U1 MIT Yes Details →
2025.12.5 06 Jan 2026 M1 U1 MIT Yes Details →
2025.12.4 31 Dec 2025 M1 U1 MIT Yes Details →
2025.12.3 30 Dec 2025 M1 U1 MIT Yes Details →
2025.12.2 23 Dec 2025 M1 U1 MIT Yes Details →
2025.12.1 19 Dec 2025 M1 U1 MIT Yes Details →
2025.12.0 16 Dec 2025 M1 U1 MIT Yes Details →
2025.12.0b5 16 Dec 2025 M1 U1 MIT Yes Details →
2025.12.0b4 16 Dec 2025 M1 U1 MIT Yes Details →
2025.12.0b3 15 Dec 2025 M1 U1 MIT Yes Details →
2025.12.0b2 12 Dec 2025 M1 U1 MIT Yes Details →
2025.12.0b1 10 Dec 2025 M1 U1 — Yes Details →
2025.11.5 09 Dec 2025 M1 U1 — Yes Details →
2025.11.4 05 Dec 2025 M1 U1 — Yes Details →
2025.11.3 03 Dec 2025 M1 U1 — Yes Details →
2025.11.2 27 Nov 2025 M1 U1 — Yes Details →
2025.11.1 24 Nov 2025 M1 U1 — Yes Details →
2025.11.0 19 Nov 2025 M1 U1 — Yes Details →
2025.11.0b5 19 Nov 2025 M1 U1 — Yes Details →
2025.11.0b4 19 Nov 2025 M1 U1 — Yes Details →
2025.11.0b3 17 Nov 2025 M1 U1 — Yes Details →
2025.11.0b2 13 Nov 2025 M1 U1 — Yes Details →
2025.11.0b1 12 Nov 2025 M1 U1 — Yes Details →
2025.10.5 12 Nov 2025 M1 U1 — Yes Details →
2025.10.4 04 Nov 2025 M1 U1 — Yes Details →
2025.10.3 24 Oct 2025 M1 U1 — Yes Details →
2025.10.2 20 Oct 2025 M1 U1 — Yes Details →
2025.10.1 16 Oct 2025 M1 U1 — Yes Details →
2025.10.0 15 Oct 2025 M1 U1 — Yes Details →
2025.10.0b4 14 Oct 2025 M1 U1 — Yes Details →
2025.10.0b3 14 Oct 2025 M1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2024 3
  • 2025 1
  • 2026 6

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

03 Vulnerabilities

Recorded vulnerabilities for esphome

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-29019: Authentication bypass via Cross site request forgery in ESPHome 8.1 high 2024.3.0 21 Mar 2024
CVE-2024-29019: ESPHome Authentication Bypass via Cross-Site Request Forgery 8.1 high 2024.3.0 07 Jul 2026
CVE-2025-57808: ESPHome web_server Basic Auth Bypass Vulnerability 8.1 high 2025.8.1 02 Sep 2025
CVE-2025-57808: ESPHome Web Server Basic Auth Bypass Vulnerability 8.1 high 2025.8.1 07 Jul 2026
CVE-2021-41104: Basic auth bypass in esphome 7.5 high 2021.9.2 29 Sep 2021

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 esphome

Is esphome safe to use?

Vulert records 12 vulnerabilities for esphome in PyPI: 0 critical, 4 high, 2 medium and 0 low, plus 6 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 esphome's Vulert package health score?

Vulert scores esphome 78/100, which reads as in good shape. 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 esphome affected?

Yes. 2026.10.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does esphome have?

12 vulnerabilities are recorded for esphome in the PyPI ecosystem: 0 critical, 4 high, 2 medium and 0 low, plus 6 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 esphome vulnerabilities disclosed?

6 vulnerabilities were recorded for esphome in the last 12 months, and the oldest entry in this database dates to 28 Sep 2021. 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 esphome 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 esphome for upcoming vulnerabilities?

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