Answer in brief
CVE-2026-130091 records a High severity (CVSS 7.1) vulnerability in temporal-proxy can be terminated by memory exhaustion when decompressing stored payloads. The current sources do not mark it as known exploited. The current feed maps Temporal Technologies, Inc./github.com/temporalio/temporal-proxy (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Temporal Technologies, Inc./github.com/temporalio/temporal-proxy (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Temporal Technologies, Inc./github.com/temporalio/temporal-proxygeneric | >=1.2.0 <1.2.1 | 1.2.1 |
Published upstream
Nov 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.