CVE-2026-130091: temporal-proxy · Data Amplification
Affects temporal-proxySource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 1.2.1 soon.
Data as of 18 Nov 2026, 20:49 UTC
Thin evidence
One scorer or none| CNA (Temporal) | CVSS 4.0 | 7.1 |
|---|
- Patch
- Available – fixed in 1.2.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade temporal-proxy and github.com/temporalio/temporal-proxy to 1.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| temporal-proxygithub.com/temporalio/temporal-proxy | Affected
| Fixed in
|
Gogithub.com/temporalio/temporal-proxypkg:golang/github.com/temporalio/temporal-proxyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/codec.go (opens in a new tab)
- github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/compressor.go (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/295 (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/ea70ede864cdf6aa9591432d0464a6d6f3413260 (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/301 (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/5c5060cc77c8e94a01de1414cc32e55751580381 (opens in a new tab)
- github.com/temporalio/temporal-proxy/releases/tag/v1.2.1 (opens in a new tab)