Skip to main content
VulnerabilityPublished

CVE-2026-132559: temporal-proxy · Improper Removal of Sensitive Information Before Storage or Transfer

Affects temporal-proxySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low · fixed in 1.2.1 : update temporal-proxy when convenient.

Data as of 18 Nov 2026, 20:49 UTC

CVSS 4.0 base score
2.3Low
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.02.3
Patch
Available – fixed in 1.2.1, 1.1.2, 1.0.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/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, 1.1.2 or 1.0.2.

Affected software

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

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

Description

When payload encryption is enabled, failure messages and stack traces that temporal-proxy is configured to keep from the upstream Temporal service can reach it in plaintext, where anyone who can read the Workflow's history at the upstream can read them. When the proxy returns a failure to a Worker, it decrypts the failure's encoded attributes and copies the message and stack trace back onto the failure, keeping the attributes. A Worker that sends that failure back through the proxy, as SDKs do when an Activity failure becomes the cause of a Workflow failure, sends the restored text with it, and the proxy forwards the text unchanged because the failure already has encoded attributes. The upstream then stores the text in plaintext beside its encrypted copy. This affects deployments that enable failure encryption in the proxy, and deployments that leave it off while the SDK encodes failure attributes itself. Payloads are not affected. temporal-proxy versions 0.9.0 through 1.2.0 are affected. Upgrade to the fixed release for the deployed minor release line.

References

Community reviews

Loading reviews…