CVE-2026-130091
A caller with write permission in a namespace can terminate …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/codec.go#L157-L166
- github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/compressor.go#L206-L262
- github.com/temporalio/temporal-proxy/commit/5c5060cc77c8e94a01de1414cc32e55751580381
- github.com/temporalio/temporal-proxy/commit/ea70ede864cdf6aa9591432d0464a6d6f3413260
- github.com/temporalio/temporal-proxy/pull/295
- github.com/temporalio/temporal-proxy/pull/301
- github.com/temporalio/temporal-proxy/releases/tag/v1.2.1
- nvd.nist.gov/vuln/detail/CVE-2026-130091
- cve.org/CVERecord?id=CVE-2026-130091
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.