Skip to main content
VulnerabilityPublished

CVE-2026-130091: temporal-proxy · Data Amplification

Affects temporal-proxySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 1.2.1 soon.

Data as of 18 Nov 2026, 20:49 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Temporal)CVSS 4.07.1
Patch
Available – fixed in 1.2.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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade temporal-proxy and github.com/temporalio/temporal-proxy to 1.2.1.

Affected software

ProductAffectedFixed in
temporal-proxygithub.com/temporalio/temporal-proxyAffected
  • >=1.2.0 <1.2.1
Fixed in
  • 1.2.1
Gogithub.com/temporalio/temporal-proxypkg:golang/github.com/temporalio/temporal-proxyOther threatsAffected
  • >=1.2.0 <1.2.1
Fixed in
  • 1.2.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…