CVE-2026-130091
High 7.1No known exploitationFix availabletemporal-proxy can be terminated by memory exhaustion when decompressing stored payloads
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 42% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Weakness: CWE-409
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Temporal))
- Fix documented (source date)
- 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.
- Mitigation
- 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.
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Temporal Technologies, Inc. | temporal-proxy | from 1.2.0 before 1.2.1 | 1.2.1 | CVE Program |
Timeline
Disclosure
CVE record published by Temporal
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Temporal)
Vendor guidance and references
- Backport commit on releases/v1.2.x (opens in a new tab)patch
- Fix commit (opens in a new tab)patch
- Fix pull request (opens in a new tab)patch
- Backport pull request for the 1.2 release line (opens in a new tab)patch
- temporal-proxy 1.2.1 (opens in a new tab)release-notes
- Inbound codec chain in temporal-proxy 1.2.0, which always includes the decompressor (opens in a new tab)product
- Compressor.Decode in temporal-proxy 1.2.0, which bounds each payload but not the response (opens in a new tab)product