CVE-2026-130091
Temporal Technologies temporal-proxy memory exhaustion in payload decompression
A remote user with write access can crash the proxy by storing small compressed payloads that exhaust its memory.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-130091 divulgada · CVSS 7.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: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
A remote user with write access to a namespace can crash temporal-proxy by storing many small, highly compressed payloads in Workflow history, which exhausts the proxy's memory when it decompresses them on read. The proxy decompresses these payloads even when compression is not configured, so the stored history causes the same crash on every later read.
Every temporal-proxy 1.2.0 deployment is affected, with no compression, encryption, or codec server setting required. Fixed in 1.2.1.
Descripción original del registro (Temporal)
A caller with write permission in a namespace can terminate temporal-proxy through memory exhaustion by storing highly compressed payloads in Workflow history, and the stored history causes the same failure on every later read. temporal-proxy 1.2.0 decompresses every payload marked as compressed in the responses it forwards, whether or not compression is configured. Each payload is limited to 4 MiB after decompression, but the total for a response is not, and the decoded payloads are held in memory together. The caller can store many small, highly compressed payloads through the proxy or directly at the upstream Temporal service. When that history is read through the proxy, for example by a Worker processing a task, the proxy can run out of memory and be terminated. The codec server's /decode endpoint is affected in the same way when it is enabled. Only temporal-proxy 1.2.0 is affected; earlier versions do not decompress payloads. The issue is fixed in 1.2.1. Upgrade to 1.2.1 or later.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/temporalio/temporal-proxy |
Sin parche | — | — | v0.9.1 no afectada |
1.2.1Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/temporalio/temporal-proxy/pull/295https://github.com/temporalio/temporal-proxy/commit/ea70ede864cdf6aa9591432d0464a6d6f3413260https://github.com/temporalio/temporal-proxy/pull/301https://github.com/temporalio/temporal-proxy/commit/5c5060cc77c8e94a01de1414cc32e55751580381https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/codec.go#L157-L166https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/compressor.go#L206-L262https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
