Skip to main content
CVE-2026-130091VulnerabilityPublished

Caller with Write Permission

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130091· High 7.1

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

Data as of 18 Nov 2026, 22: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.

AI-suggested

Upgrade temporal-proxy to version 1.2.1 or later, where this vulnerability is fixed. No other mitigations are indicated or required.

Description

Temporal-proxy version 1.2.0 contains a vulnerability where a caller with write permission in a namespace can cause the proxy to terminate due to memory exhaustion. This occurs by storing highly compressed payloads in Workflow history that decompress to large sizes, causing the proxy to consume excessive memory when reading the history. The issue affects the /decode endpoint of the codec server when enabled. The vulnerability is fixed in version 1.2.1.

References

Community reviews

Loading reviews…