CVE-2026-130091 json
temporal-proxy can be terminated by memory exhaustion when decompressing stored payloads
published 4h ago modified 2h ago also EUVD-2026-129188
- cvss
- 7.1
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Temporal Technologies, Inc. temporal-proxy 1.2.1
Is CVE-2026-130091 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.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:N |
Affected products
- Temporal Technologies, Inc. temporal-proxy
Classification
- Weakness
-
- CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
References
-
github.com
/temporalio/temporal-proxy/pull/295
patch
-
github.com
/temporalio/temporal-proxy/commit/ea70ede864cdf6aa9591432d0464a6d6f3413260
patch
-
github.com
/temporalio/temporal-proxy/pull/301
patch
-
github.com
/temporalio/temporal-proxy/commit/5c5060cc77c8e94a01de1414cc32e55751580381
patch
-
github.com
/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/codec.go#L157-L166
product
-
github.com
/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/compressor.go#L206-L262
product
-
github.com
/temporalio/temporal-proxy/releases/tag/v1.2.1
release-notes
Sources
- CVE List CVE-2026-130091
- NVD CVE-2026-130091
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.