Skip to content
Threat Brief

← All advisories

CVE-2026-132559

Low 2.3No known exploitationFix available

temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext

Record last updated

CVSS score

2.3

Low on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 43% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line.

Weakness: CWE-212

Patching and mitigation

Patch status
Fix available (source: CVE record (Temporal))
Fix documented (source date)
Vendor solution
Upgrade to temporal-proxy 1.0.2, 1.1.2, or 1.2.1, as appropriate for the deployed minor release line. Fixed releases replace the message and clear the stack trace of every outbound failure that carries encoded attributes, in any encoding, whenever the proxy is configured with encryption keys, whether or not encryption.failures is set. A custom failure converter that sends readable text beside its own encoded attributes will find that text replaced at the upstream. Upgrading does not re-encrypt failure text the upstream already stores. Releases before 1.0.0 receive no fix.
Mitigation
No proxy setting closes this issue: with encryption.failures off, the proxy still restores failure text that the SDK encoded, and a Worker that sends it back still sends it in plaintext. Until a fixed release is deployed, keep sensitive data out of failure messages and stack traces.
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Temporal Technologies, Inc.temporal-proxyfrom 0.9.0 up to and including 0.10.1Not documentedCVE Program
Temporal Technologies, Inc.temporal-proxyfrom 1.0.0 before 1.0.21.0.2CVE Program
Temporal Technologies, Inc.temporal-proxyfrom 1.1.0 before 1.1.21.1.2CVE Program
Temporal Technologies, Inc.temporal-proxyfrom 1.2.0 before 1.2.11.2.1CVE Program

Timeline

  1. Disclosure

    CVE record published by Temporal

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Temporal)

    Source: CVE record (Temporal) (opens in a new tab)

Vendor guidance and references