The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Sunday, 22 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

CVE-2026-38427: Tasmota Flaw Risks Smart Devices

By The Daily Byte ·22 Nov 2026 ·2 min read
An ESP32 development board, the hardware Tasmota firmware runs on

Public exploit code for a heap overflow in Tasmota, the open-source firmware for smart-home switches, plugs and bulbs, was listed by the exploit tracker KitPloit today. The vulnerability, tracked as CVE-2026-38427, sits in the fetch_jpg function of Tasmota's scripting engine and affects versions up to and including 15.3.0.3. The fix shipped in version 15.3.0.4.

The bug is an integer wraparound. When a Tasmota device fetches MJPEG frames from a server, it reads the Content-Length header into a 16-bit unsigned integer. Values above 65,535 silently wrap around: a length of 65,537 becomes 1, and 70,000 becomes 4,464. The device then allocates a heap buffer far too small for the data that follows, reads only the wrapped number of bytes, and leaves the rest sitting in the stream, corrupting the device's memory state. The reliable result is a crash and reboot; on ESP32 hardware the researcher says remote code execution is possible.

Researcher Saidakbarxon Maxsudxonov reported the flaw under responsible disclosure and published the proof of concept with a working fake MJPEG server. The CVE was assigned on 29 March 2026 and the patched release followed in May. NVD records a CVSS 3.1 score of 7.3, rated High, while the researcher describes the flaw as critical in the proof-of-concept write-up.

How an attack would work

This is not a flaw an attacker can trigger by scanning the internet. The device has to be made to fetch images from the attacker's server, either through a malicious Tasmota script using the fetchjp command or by intercepting the device's traffic. That limits the exposure, but it does not remove it: a compromised device on the same network, or a script copied from an untrusted source, can supply the trigger.

The proof of concept demonstrates the crash with Content-Length values of 65,537 and 131,072, both of which wrap to tiny allocations while tens of kilobytes remain unread.

Who should update

Anyone running Tasmota on ESP8266 or ESP32 hardware should check the installed version and update to 15.3.0.4 or later. Scripts that fetch images from unfamiliar servers should be reviewed, and the fetchjp command should only point at servers the owner controls. Smart-home devices rarely get the patching attention of phones and laptops, but they sit on the same home network, and a compromised switch is a foothold to everything else.

Source
GitHub (proof-of-concept by Saidakbarxon Maxsudxonov) — https://github.com/sermikr0/cve-2026-38427