Skip to main content
Menu
CVEs

CVE

Temporal Technologies temporal-proxy memory exhaustion in payload decompression

Every temporal-proxy 1.2.0 deployment is affected, with no compression, encryption, or codec server setting required. Fixed in 1.2.1.

CVE-2026-130091EUVD-2026-129188Published Updated Summary written by a model

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.2.1
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Every temporal-proxy 1.2.0 deployment is affected; no compression, encryption, or codec server setting is required. The attacker needs write permission in one namespace whose history is read through the proxy.

Summary

A remote user with write access to a namespace can crash temporal-proxy by storing many small, highly compressed payloads in Workflow history, which exhausts the proxy's memory when it decompresses them on read. The proxy decompresses these payloads even when compression is not configured, so the stored history causes the same crash on every later read.

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

Who should check

Teams running temporal-proxy 1.2.0, in any deployment, whose Workflow history is read through the proxy by Workers or codec server clients.

Not fixed by: Terminating or resetting Workflow Executions does not remove the stored history.

“Every temporal-proxy 1.2.0 deployment is affected”

cve.org

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Every temporal-proxy 1.2.0 deployment is affected; no compression, encryption, or codec server setting is required. The attacker needs write permission in one namespace whose history is read through the proxy.
  • Upgrade to a fixed version: 1.2.1.

  • Workaround: Run temporal-proxy 1.1.2 on the 1.1 release line, which does not decompress payloads; only possible for deployments that have not enabled compression.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130091 (temporal-proxy can be terminated by memory exhaustion when decompressing stored payloads), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130091 (entry last updated 2026-11-18):
Affected:
- Go package github.com/temporalio/temporal-proxy: from 1.2.0, fixed in 1.2.1
Fixed versions: 1.2.1.
Conditions (all must be true for the bug to be hit):
- Every temporal-proxy 1.2.0 deployment is affected; no compression, encryption, or codec server setting is required. (source: https://www.cve.org/CVERecord?id=CVE-2026-130091)
- The attacker needs write permission in one namespace whose history is read through the proxy. (source: https://www.cve.org/CVERecord?id=CVE-2026-130091)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Run temporal-proxy 1.1.2 on the 1.1 release line, which does not decompress payloads; only possible for deployments that have not enabled compression. (source: https://www.cve.org/CVERecord?id=CVE-2026-130091)
CISA KEV: CVE-2026-130091 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130091 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/temporalio/temporal-proxy/pull/295
- https://github.com/temporalio/temporal-proxy/commit/ea70ede864cdf6aa9591432d0464a6d6f3413260
- https://github.com/temporalio/temporal-proxy/pull/301
- https://github.com/temporalio/temporal-proxy/commit/5c5060cc77c8e94a01de1414cc32e55751580381
- https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/codec.go#L157-L166
- https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/compressor.go#L206-L262
- https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1
- https://www.cve.org/CVERecord?id=CVE-2026-130091
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130091
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130091"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 9

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130091

Is CVE-2026-130091 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A bug in temporal-proxy lets memory exhaustion terminate the proxy while it decompresses stored payloads. The attacker needs write permission in one namespace whose history is read through the proxy.Source: cve.org

Which versions are affected by CVE-2026-130091?

github.com/temporalio/temporal-proxy (Go): from 1.2.0 before 1.2.1.Source: cve.now feed data

Am I affected, and how do I check?

The range is temporal-proxy from 1.2.0 up to, but not including, 1.2.1. The advisory says every 1.2.0 deployment is affected, and no compression, encryption, or codec server setting is required. To check a deployment, look at the installed temporal-proxy version.Source: cve.org

How do I fix CVE-2026-130091?

Upgrade to temporal-proxy 1.2.1 or later.Source: cve.org

More CVEs