EudorIACyber Intelligence
Operational monitoring Newsletter IT EN
← Back to intelligence
Vulnerability

CVE-2026-17054: The Espressif ESP-hosted Wi-Fi driver (drivers/wifi/esp_hosted/) parses frames received over SPI from the ESP co-processor in esp_hosted_event_task(). For control frames it took the 16-bit TLV field data_length straight

Official source
EudorIA operational summary

What it means

Priority 45/100

NIST National Vulnerability Database ha pubblicato CVE-2026-17054. La rilevanza va confermata rispetto alle tecnologie effettivamente in uso.

Why it matters

Il segnale diventa operativo solo se prodotto, versione o servizio sono presenti nel perimetro.

AudienceITSOCCISO
Information centre

Translation in progress

NIST National Vulnerability Database

The official content is available in the original language. The Italian version will be published once automated checks are complete.

Text acquired from the source

The Espressif ESP-hosted Wi-Fi driver (drivers/wifi/esp_hosted/) parses frames received over SPI from the ESP co-processor in esp_hosted_event_task(). For control frames it took the 16-bit TLV field data_length straight off the wire and passed it to pb_istream_from_buffer(frame.data_value, frame.data_length) without checking it against the frame length or the receive buffer. frame.data_value sits 26 bytes into a 3188-byte stack object, so a data_length of up to 0xFFFF makes pb_decode() read up to roughly 62 KB past the end of that object. Only the first fragment of a fragmented control response carries a TLV header; the pre-fix driver performed half-duplex SPI transactions and silently discarded any frame the co-processor queued while the host was transmitting (esp_hosted_hal_spi_transfer() aliased the RX buffer onto the TX buffer). When the discarded frame is the first fragment of a fragmented response, the driver treats the next fragment as a new frame — its per-fragment header and checksum are genuine, so both validation steps pass — and reads the TLV header out of raw protobuf continuation bytes. Those bytes come from control responses whose size and content an adjacent, unauthenticated attacker can influence, notably the AP scan list, which grows with the number and SSID length of access points in radio range. The impact is denial of service rather than disclosure. Reading past the end of the RAM region faults the device, and CONFIG_NANOPB_ENABLE_MALLOC is selected by the driver, so garbage length prefixes read out of bounds also drive heap allocations. The out-of-bounds bytes themselves do not reach the application: pb_decode() is started mid-stream on raw protobuf continuation bytes and so almost always fails outright, and anything that did decode would still hav

Source
NIST National Vulnerability Database
Publishing entity
NIST National Vulnerability Database
Entity type
National authority
Area
North America · US
Original language
en · translation in preparation
Publication
22/09/2026 00:16
CVE
CVE-2026-17054
Classification
Medium
Stated country
US
Technical scope

Affected products and versions

Not published
No structured range published.

The official sources queried do not yet expose a list of affected versions. No automatic inference is made.

Sources for the versionsNIST National Vulnerability Database
Open the original source