llamaCVEVulnerability Intelligence
/
Temporal Technologies temporal-proxy

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.

Solo en configuraciones específicasSin parche publicadodecompression bomb
Descargar PNG JSON
CVSS 4.0
7.1
Alta
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
ExplotaciónSin evidenciaSSVC: ninguna · no figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición2 dDesde la divulgación, 18 nov 2026, 3:24 p. m.
Detección10 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, no automatizable e impacto técnico parcial. No hay versión corregida: aplique mitigaciones.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada
Fuente: NIST NVD +1
Verificada
03:24 p. m.
04:19 p. m.
05:23 p. m.
02:32 a. m.
03:24 p. m.
06:11 a. m.
08:58 p. m.
11:45 a. m.
02:32 a. m.
FechaFaseEventoDetalle
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
Resumen
Resumen generado por IA · CC-BY 4.0 · 18 nov 2026

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.

¿Qué significa?A bug in temporal-proxy lets memory exhaustion terminate the proxy while it decompresses stored payloads. The attacker needs write permission in one namespace whose history is read through the proxy.
¿Quién está afectado?The range is temporal-proxy from 1.2.0 up to, but not including, 1.2.1. The advisory says every 1.2.0 deployment is affected, and no compression, encryption, or codec server setting is required. To check a deployment, look at the installed temporal-proxy version.
¿Qué hacer?Upgrade to temporal-proxy 1.2.1 or later.
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.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Every temporal-proxy 1.2.0 deployment is affected; no compression, encryption, or codec server setting is required.“Every temporal-proxy 1.2.0 deployment is affected”
02
The attacker needs write permission in one namespace whose history is read through the proxy.“The attacker needs write permission in one namespace whose history is read through the proxy.”
¿Quién debe revisar?Teams running temporal-proxy 1.2.0, in any deployment, whose Workflow history is read through the proxy by Workers or codec server clients.
No protegeTerminating or resetting Workflow Executions does not remove the stored history.
MitigaciónRun temporal-proxy 1.1.2 on the 1.1 release line, which does not decompress payloads; only possible for deployments that have not enabled compression.
Vector CVSS 4.0

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
Requisitos de ataqueAT:N
NingunoPresentes
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaPasivaActiva
Confid. (sistema)VC:N
AltoBajoNinguno
Integridad (sistema)VI:N
AltoBajoNinguno
Disponib. (sistema)VA:H
AltoBajoNinguno
Confid. (posterior)SC:N
AltoBajoNinguno
Integridad (posterior)SI:N
AltoBajoNinguno
Disponib. (posterior)SA:N
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
8.3/ 10Alto
Vector 8.3 (muy fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida Última
github.com/temporalio/temporal-proxy≥ 1.2.0 < 1.2.1
v0.9.1
1.2.0
1.2.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogithub.com/temporalio/temporal-proxy
Sin parche — — v0.9.1 no afectada
Versiones corregidas1.2.1
Explotación

Arsenal público

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

Registro
EscenarioGENERALTemporal
configurationEvery temporal-proxy 1.2.0 deployment is affected; no compression, encryption, or codec server setting is required. The attacker needs write permission in one namespace whose history is read through the proxy.Temporal
configurationThe Subsequent System Availability metric is None because the upstream Temporal service keeps running and serving clients that do not use the proxy; loss of the proxy's own service is scored as Vulnerable System Availability.Temporal
MitigaciónNo setting disables the decoder in 1.2.0. A deployment that has not enabled compression can run 1.1.2 on the 1.1 release line, which does not decompress payloads; one that enabled compression on 1.2.0 cannot, because 1.1 passes the stored compressed payloads to clients undecoded. Deleting the Workflow Executions that hold the payloads stops the repeated failures; terminating or resetting them does not remove the history.Temporal
solutionUpgrade to temporal-proxy 1.2.1 or later. Fixed releases limit the bytes decoded for one response to its upstream's maxResponseSize, and the bytes held at once across every response and codec server request to compression.maxDecodedInFlight, 512 MiB by default; a response that would exceed either limit is refused with ResourceExhausted. A configuration whose maxResponseSize exceeds compression.maxDecodedInFlight must raise compression.maxDecodedInFlight to match, or the proxy does not start.Temporal
Referencias
Parchehttps://github.com/temporalio/temporal-proxy/pull/295
Parchehttps://github.com/temporalio/temporal-proxy/commit/ea70ede864cdf6aa9591432d0464a6d6f3413260
Parchehttps://github.com/temporalio/temporal-proxy/pull/301
Parchehttps://github.com/temporalio/temporal-proxy/commit/5c5060cc77c8e94a01de1414cc32e55751580381
Otrahttps://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/codec.go#L157-L166
Otrahttps://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/compressor.go#L206-L262
Otrahttps://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1

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