llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Go · github.com/dunglas/frankenphp

GHSA-5359-VG53-5464

A failed PHP request startup can crash the server with a segmentation fault

Texto original en inglés · Ver en español

Parche disponible
Descargar PNG JSON
CVSS 3.1
5.9
Media
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche el mismo día de la divulgación
Exposición16 dDesde la divulgación, 5 nov 2026, 7:01 a. m.
Detección14 dDesde la divulgación hasta su ingreso al índice
Decisión estimadaSeguir
Remediar en la ventana regular de mantenimiento
Estimación de Llama con el árbol SSVC de CISA a partir de vector CVSS 3.1 y la evidencia de explotación (sin evaluación oficial): sin explotación conocida, no automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Tranqui, va para la ventana de mantenimiento.Si haces parches mensuales, ya estás cubierto.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Parche v1.13.5
Monitoreo
Detectada +1
5 nov 26
19 nov 26
21 nov 26
5 nov 26
9 nov 26
13 nov 26
17 nov 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-5359-VG53-5464 divulgada · CVSS 5.9 (GitHub)
Divulgación Modificada Última actualización del registro
Remediación Parche v1.13.5 github.com/dunglas/frankenphp · 0 d desde divulgación
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
Impact

An unauthenticated client can crash the whole FrankenPHP process, with every site and in-flight request it serves, by making PHP's request startup fail repeatedly on a regular (non-worker) thread. Two triggers were confirmed:

  • A request with more query or form parameters than `max_input_vars`, whose client hangs up before the response. This needs `display_errors=1`, `display_startup_errors=1` and `output_buffering=0`, which are PHP's built-in defaults and apply when no `php.ini` is loaded, as in the official Docker images.
  • A `application/x-www-form-urlencoded` POST body large enough to exhaust `memory_limit` while `$_POST` is built. This works with production settings once `post_max_size` is raised to about a quarter of `memory_limit` or more.

Scripts served by workers are not affected. A few dozen requests on two connections were enough in testing. Short of the crash, each failed startup cost a full PHP thread teardown and restart.

Patches

Fixed in 1.13.5.

Workarounds

Load a `php.ini` with `display_errors=0` or `output_buffering=4096` (both PHP templates set the latter), and keep `post_max_size` well below `memory_limit`. These close the known triggers but not the underlying failure handling.

Details

When `php_request_startup()` failed, `php_thread()` treated the thread as unhealthy: it forced `php_request_shutdown()`, freed the thread's TSRM context and started a new thread. The new thread's module globals are allocated with `malloc()` and only initialized by each extension's GINIT. ext/date sets `DATEG(last_errors)` in RINIT only, but its post-deactivate hook, which `php_request_shutdown()` always runs, frees it. When the first request of a new thread also failed during startup, before any RINIT ran, ext/date passed an uninitialized pointer to `efree()` and the process died with a segmentation fault.

A client hang-up was enough to fail the startup: the "Input variables exceeded" warning is written to the client while `$_GET` is built, and the SAPI bailed out on a closed connection because regular threads run with `ignore_user_abort=0`. A fatal error such as an exhausted `memory_limit` during `$_POST` parsing has the same effect without a hang-up.

The fix:

  • The SAPI no longer bails out on a closed connection during request startup; the script's first write notices the abort, as when output buffering is on.
  • A failed request startup now ends only that request, with a regular request shutdown and a 500 status if headers were not sent, and the thread keeps serving requests.

With threads no longer replaced, the uninitialized `DATEG(last_errors)` can only be reached when the very first request of a thread, including a thread added by autoscaling, fails during startup through a fatal error such as an exhausted `memory_limit`, which requires `post_max_size` above about a quarter of `memory_limit`. Keeping `post_max_size` well below `memory_limit` avoids it. ext/date should initialize it in its GINIT; this is being reported to PHP separately.

The failure handling was introduced in 1.12.2. Before that version, a failed request startup caused a Go panic that exited the process, so older versions are also affected.

Proof of concept

No `php.ini`, PHP's built-in defaults:

$ frankenphp php-server --listen 127.0.0.1:8080

`hello.php`:

<?php echo "hello\n";

Send, two at a time, a request to `/hello.php` with 1100 query parameters (`?v0=1&v1=1&...&v1099=1`) and close the write side of the socket right after sending it. After a few dozen requests the process exits with SIGSEGV in `zm_post_zend_deactivate_date()` called from `php_request_shutdown()`.

Credits

Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-CDG8FSAB.

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:N
AltoBajoNinguno
IntegridadI:N
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
7.1/ 10Alto
Vector 7.1 (fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida Última
github.com/dunglas/frankenphp≤ 1.13.4
1.13.4
v1.13.6
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogithub.com/dunglas/frankenphp
Corregida v1.13.5 0 d v1.13.6 no afectada
Versiones corregidasv1.13.5
Explotación

Arsenal público

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

Referencias
Advisoryhttps://github.com/php/frankenphp/security/advisories/GHSA-5359-vg53-5464

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