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

Summary

CVECVE-2026-130091
StatePUBLISHED
AssignerTemporal
Source PriorityCVE Program / NVD first with legacy fallback
Published2026-11-18 21:17:49 UTC
Updated2026-11-18 22:17:18 UTC
DescriptionA 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.

Risk And Classification

Primary CVSS: v4.0 7.1 HIGH from [email protected]

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

EPSS: 0.004720000 probability, percentile 0.415610000 (date 2026-11-19)

Problem Types: CWE-409 | CWE-409 CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)


VersionSourceTypeScoreSeverityVector
4.0[email protected]Secondary7.1HIGHCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/C...
4.0CNACVSS7.1HIGHCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS v4.0 Breakdown

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Confidentiality
None
Integrity
None
Availability
High
Sub Conf.
None
Sub Integrity
None
Sub Availability
None

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Vendor Declared Affected Products

SourceVendorProductVersionPlatforms
CNA Temporal Technologies Inc. Temporal-proxy affected 1.2.0 1.2.1 semver Not specified

References

ReferenceSourceLinkTags
github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/codec.go [email protected] github.com
github.com/temporalio/temporal-proxy/commit/5c5060cc77c8e94a01de1414cc32... [email protected] github.com
github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/compressor.go [email protected] github.com
github.com/temporalio/temporal-proxy/releases/tag/v1.2.1 [email protected] github.com
github.com/temporalio/temporal-proxy/commit/ea70ede864cdf6aa9591432d0464... [email protected] github.com
github.com/temporalio/temporal-proxy/pull/295 [email protected] github.com
github.com/temporalio/temporal-proxy/pull/301 [email protected] github.com
CVE Program record CVE.ORG www.cve.org canonical
NVD vulnerability detail NVD nvd.nist.gov canonical, analysis

Additional Advisory Data

Solutions

CNA: 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.

Workarounds

CNA: 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.

© CVE.report 2026

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

Free CVE JSON API cve.report/api

CVE.report and Source URL Uptime Status status.cve.report