CVE-2026-130091
Received Received - Intake

Memory Exhaustion in Temporal Proxy via Compressed Payloads

Vulnerability report for CVE-2026-130091, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: Temporal Technologies Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Temporal Technologies, Inc. temporal-proxy From 1.2.0 (inc) to 1.2.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-409 The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects temporal-proxy version 1.2.0. A user with write permissions in a namespace can cause memory exhaustion by storing highly compressed payloads in Workflow history. When these payloads are read through the proxy, it decompresses all payloads marked as compressed, even if compression is not configured. Each payload is limited to 4 MiB after decompression, but the total size of all decoded payloads in a response is not limited. This can cause the proxy to run out of memory and terminate. The codec server's /decode endpoint is also affected. The issue is fixed in version 1.2.1.

The vulnerability occurs because temporal-proxy 1.2.0 does not enforce limits on the total size of decoded payloads in a response or the cumulative size of all in-flight responses. This allows an attacker to store many small, highly compressed payloads that expand significantly when decompressed.

Detection Guidance

Monitor memory usage on systems running temporal-proxy 1.2.0 during workflow processing. Check for repeated ResourceExhausted errors in logs when decoding compressed payloads. Use metrics endpoints to track in-flight decoded payload sizes and total memory consumption.

Impact Analysis

If you use temporal-proxy 1.2.0, an attacker with write access to a namespace could cause the proxy to crash by storing compressed payloads. This would disrupt workflow processing, potentially leading to service outages or data loss. The codec server's /decode endpoint could also be affected, causing similar issues if enabled.

Compliance Impact

The vulnerability could lead to denial-of-service (DoS) conditions by exhausting memory in temporal-proxy, potentially disrupting services handling sensitive data. This may impact compliance with GDPR (availability of processing systems) and HIPAA (availability of healthcare data systems) by causing service disruptions or unauthorized termination of data processing workflows.

Mitigation Strategies

Upgrade temporal-proxy to version 1.2.1 or later. Configure DecodeLimiter and ResponseLimit in proxy.CodecOptions. Set compression.maxDecodedInFlight to a safe value (default 512MiB) and adjust if maxResponseSize exceeds this limit.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130091. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...