llamaCVEVulnerability Intelligence
/
Zephyr

CVE-2026-82391

Zephyr remote code execution in HTTP server static file handler

A remote attacker with no login can send a crafted request that corrupts server memory and may crash the server.

UnclearParche disponibleout-of-bounds write
Descargar PNG JSON
CVSS 3.1
9.1
Crítica
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versiones4.3.2 · 4.5.0
Exposición8 dDesde la divulgación, 10 nov 2026, 5:07 p. m.
Detección16 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada
Fuente: OSV
Verificada
10 nov 26
13 nov 26
16 nov 26
19 nov 26
10 nov 26
13 nov 26
15 nov 26
17 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-82391 divulgada · CVSS 9.1 (CNA)
Monitoreo Detectada Ingresó al índice
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 10 nov 2026

Zephyr's HTTP server is affected when it serves static files over HTTP/2. A remote attacker who has no login can send a crafted GET request for a file under the web root and corrupt memory in the server, which could lead to high integrity and availability impact.

Affects Zephyr 4.0.0 before 4.3.2 and 4.4.0 before 4.5.0 with the HTTP/2 server serving a static-filesystem resource. Fixed in Zephyr 4.3.2 and 4.5.0.

¿Qué significa?A corrupted receive-buffer length in the HTTP/2 server's static-filesystem handler lets a write go past the end of its buffer. Zephyr runs in a single address space, so this corrupts memory and can at minimum crash or hang the device.
¿Quién está afectado?Affected are Zephyr 4.0.0 before 4.3.2 and 4.4.0 before 4.5.0 where HTTP/2 server support is enabled (CONFIG_HTTP_SERVER_VERSION_2, on by default) and an application registers a static-filesystem resource with CONFIG_FILE_SYSTEM=y. To check, look at the Zephyr version in the source tree and at those two settings in the build configuration.
¿Qué hacer?Upgrade to Zephyr 4.3.2 for the 4.3 line or to 4.5.0 for the 4.4 line.
Descripción original del registro (zephyr)

The HTTP/2 front-end of the Zephyr HTTP server aliased connection receive state as a scratch output. In subsys/net/lib/http/http_server_http2.c, handle_http2_static_fs_resource() passed &client->data_len as the file_size out-parameter of http_server_find_file(). client->data_len is the count of unprocessed bytes remaining in the fixed-size per-connection receive buffer client->buffer[CONFIG_HTTP_SERVER_CLIENT_BUFFER_SIZE] (256 bytes by default), an invariant every frame handler and the socket receive path rely on. Serving any static file therefore replaced that bounded value with the file's on-disk size, and nothing resets it afterwards. The defect is reached by an unauthenticated HTTP/2 GET for any file under the web root, in applications that register a static-filesystem resource (HTTP_RESOURCE_TYPE_STATIC_FS) with CONFIG_FILE_SYSTEM=y; CONFIG_HTTP_SERVER_VERSION_2 is enabled by default and no TLS or credentials are required on this path. Once client->data_len exceeds the buffer size, the frame dispatch loop in subsys/net/lib/http/http_server_core.c keeps parsing past the end of the received data, and the peer controls the bytes at client->cursor, so it can choose which fabricated frame the state machine consumes next by appending bytes after its request. The inflated length defeats the only guards on the buffer. parse_http_frame_header() and the per-frame handlers read and skip up to a 24-bit frame length beyond the buffer (out-of-bounds read); the compaction memmove(client->buffer, client->cursor, client->data_len) at the end of request handling copies the file-size number of bytes into the 256-byte buffer, overflowing the rest of struct http_client_ctx — including the current_detail/current_stream pointers, the parser_settings function-pointer table and the inactivity_timer work handler — and the adjacent client contexts in static memory; and the subsequent zsock_recv(client->fd, client->buffer + client->data_len, sizeof(client->buffer) - client->data_len, 0) underflows its size argument, writing attacker-supplied data of attacker-chosen length out of bounds. The impact is remote memory corruption in the server's single address space: at minimum a crash or hang of the device, and plausibly control-data overwrite leading to code execution. The HTTP/1 and HTTP/3 static-filesystem handlers already used a local variable and are unaffected; the fix makes the HTTP/2 handler use a local size_t file_size as well.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
HTTP/2 server support enabled (CONFIG_HTTP_SERVER_VERSION_2, on by default)“CONFIG_HTTP_SERVER_VERSION_2 is enabled by default”
02
Application registers a static-filesystem resource (HTTP_RESOURCE_TYPE_STATIC_FS) with CONFIG_FILE_SYSTEM=y“applications that register a static-filesystem resource”
¿Quién debe revisar?Teams running Zephyr 4.0.0 up to 4.3.2, or 4.4.x before 4.5.0, that serve static files through the HTTP/2 server with a static-filesystem resource.
No protegeRelease lines that have not yet taken the backport remain affected.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:N
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
zephyr≥ 4.0.0 < 4.3.2
zephyr≥ 4.4.0 < 4.5.0
4.0.0
4.3.2
4.4.0
4.5.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
zephyr
Corregida 4.3.2, 4.5.0 — —
Versiones corregidas4.3.24.5.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-8jrg-wx88-g75j
Parchehttps://github.com/zephyrproject-rtos/zephyr/commit/4e0a5f38b14dba5891fb558c49a526f9f6a3cc29

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.