Skip to content

⬆️ Update esphome to v2025.12.7 [SECURITY]#1088

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/pypi-esphome-vulnerability
Open

⬆️ Update esphome to v2025.12.7 [SECURITY]#1088
renovate[bot] wants to merge 1 commit intomainfrom
renovate/pypi-esphome-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Jan 21, 2026

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
esphome ==2025.12.3==2025.12.7 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

CVE-2026-23833

Summary

An integer overflow in the API component's protobuf decoder allows denial-of-service attacks when API encryption is not used.

Details

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.

Affected Versions

ESPHome 2025.9.0 through 2025.12.6

Mitigation

Severity

Low - Users following Security Best Practices with API encryption enabled are not affected without knowledge of the encryption key.

Impact

Denial-of-service. An attacker with network access to port 6053 can crash and reboot the device.

Credits

Thanks to @​Mat931 for responsibly reporting this vulnerability.

Severity
  • CVSS Score: 6.8 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Release Notes

esphome/esphome (esphome)

v2025.12.7

Compare Source

v2025.12.6

Compare Source

v2025.12.5

Compare Source

v2025.12.4

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added dependencies Upgrade or downgrade of project dependencies. no-stale This issue or PR is exempted from the stable bot. python labels Jan 21, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Jan 21, 2026

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot removed the python label Jan 21, 2026
@renovate renovate bot changed the title ⬆️ Update esphome to v2025.12.7 [SECURITY] ⬆️ Update esphome to v2025.12.7 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate bot closed this Mar 27, 2026
@renovate renovate bot deleted the renovate/pypi-esphome-vulnerability branch March 27, 2026 01:48
@github-actions github-actions bot locked and limited conversation to collaborators Mar 28, 2026
@renovate renovate bot changed the title ⬆️ Update esphome to v2025.12.7 [SECURITY] - autoclosed ⬆️ Update esphome to v2025.12.7 [SECURITY] Mar 30, 2026
@renovate renovate bot reopened this Mar 30, 2026
@renovate renovate bot force-pushed the renovate/pypi-esphome-vulnerability branch 2 times, most recently from ead45f4 to 3c5bd31 Compare March 30, 2026 18:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

dependencies Upgrade or downgrade of project dependencies. no-stale This issue or PR is exempted from the stable bot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants