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

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

- **Severity:** High 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`)
- **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 available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-mhcr-64cf-9g9r

## 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 (Improper Handling of Highly Compressed Data (Data Amplification))

## 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.

## Is CVE-2026-130091 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130091 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-130091 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: temporal-proxy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130091/ (Markdown: https://insights.sbomify.com/CVE-2026-130091/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130091
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130091
- OSV: https://osv.dev/vulnerability/CVE-2026-130091

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130091/
Summaries are generated and may contain mistakes; the official description above is the record.
