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

High 7.1 Published Updated

A namespace caller can store highly compressed payloads that exhaust memory and crash temporal-proxy on later reads; Temporal operators should care.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Harmful if only installed
No
Needs a specific call
No
Fix
None listed

What is CVE-2026-130091?

CVE-2026-130091 is a high-severity denial of service vulnerability in temporal-proxy, published on 18 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official 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

Which versions are affected by CVE-2026-130091?

An affected version is exposed as installed. No special setting or call is needed.

How do I fix CVE-2026-130091?

No fix has been published for CVE-2026-130091 yet. Limit exposure of the affected software until one is available.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-130091 being exploited?

There is no known exploitation of CVE-2026-130091 in the wild and no public exploit code.

Sources

Also known as GHSA-mhcr-64cf-9g9r.

Is CVE-2026-130091 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free