Skip to content
Threat Brief

← All advisories

CVE-2026-130091

High 7.1No known exploitationFix available

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

Record last updated

CVSS score

7.1

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 42% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

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

VendorProductAffected versionsFixed inPer
Temporal Technologies, Inc.temporal-proxyfrom 1.2.0 before 1.2.11.2.1CVE Program

Timeline

  1. Disclosure

    CVE record published by Temporal

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Temporal)

    Source: CVE record (Temporal) (opens in a new tab)

Vendor guidance and references