CVE-2026-130091

temporal-proxy can be terminated by memory exhaustion when decompressing stored payloads

Published Nov 18, 2026 CVSS 4.0 · 7.1 High EPSS n/a KEV · Not listed
Description
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.

Remediation

Vendor Solution

Upgrade 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.


Vendor Workaround

No 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.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description 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.
Title temporal-proxy can be terminated by memory exhaustion when decompressing stored payloads
Weaknesses CWE-409
References
Metrics cvssV4_0

{'score': 7.1, 'vector': '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'}

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
Temporal
Published
Updated
Nov 18, 2026, 8:24 PM
Reserved
Nov 16, 2026, 8:59 PM

No data.