Nixpkgs Security Tracker

Login with GitHub

Suggestions search

With package: esphome

Found 1 matching suggestions

updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    9 packages
    • python312Packages.aioesphomeapi
    • python312Packages.bleak-esphome
    • python313Packages.aioesphomeapi
    • python313Packages.bleak-esphome
    • python312Packages.esphome-glyphsets
    • python313Packages.esphome-glyphsets
    • home-assistant-component-tests.esphome
    • python312Packages.esphome-dashboard-api
    • python313Packages.esphome-dashboard-api
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
ESPHome vulnerable to denial-of-service via out-of-bounds check bypass in the API component

ESPHome is a system to control microcontrollers remotely through Home Automation systems. In versions 2025.9.0 through 2025.12.6, an integer overflow in the API component's protobuf decoder allows denial-of-service attacks when API encryption is not used. The bounds check `ptr + field_length > end` in `components/api/proto.cpp` can overflow when a malicious client sends a large `field_length` value. This affects all ESPHome device platforms (ESP32, ESP8266, RP2040, LibreTiny). The overflow bypasses the out-of-bounds check, causing the device to read invalid memory and crash. When using the plaintext API protocol, this attack can be performed without authentication. When noise encryption is enabled, knowledge of the encryption key is required. Users should upgrade to ESPHome 2025.12.7 or later to receive a patch, enable API encryption with a unique key per device, and follow the Security Best Practices.

Affected products

esphome
  • ==>= 2025.9.0, < 2025.12.7

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/esphome/esphome/security/advisories/GHSA-4h3h-63v6-88qx
Upstream patch: https://github.com/esphome/esphome/commit/69d7b6e9210390051318bd8e6410727689de08d6