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.
Published: 2026-11-18
Score: 2.3 Low
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

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.


Vendor Workaround

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.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

References
Link Providers
https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L26-L29 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L55-L70 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/commit/53710919feb8af12e2f4b789e2d997a412cdd33f cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/commit/68dea481cdd8112432d5efb495b0963e03fff14d cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/commit/7742a645c526dde4b6a182e6e55e2f9d9ea2b43b cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/commit/85492b5728362d8fd082e5cff9290a23c016ae30 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/commit/8bd1045ccfaaa54580444dd9855fd87f3b1b252b cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/commit/95b99dceaa1a19c666b1661e2edef4090acda119 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/commit/c5d211cda68a7c07ec691b3b47f1c0ab6fc495fb cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/commit/ea541ae21fbfda65bd867a88020ddfce0b92c907 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/pull/296 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/pull/302 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/pull/303 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/pull/304 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/pull/305 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/pull/306 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/pull/307 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/pull/308 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2 cve-icon cve-icon
https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1 cve-icon cve-icon
History

Wed, 18 Nov 2026 22:00:00 +0000

Type Values Removed Values Added
First Time appeared Temporal
Temporal temporal-proxy
Vendors & Products Temporal
Temporal temporal-proxy

Wed, 18 Nov 2026 20:45:00 +0000

Type Values Removed Values Added
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.
Title temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext
Weaknesses CWE-212
References
Metrics cvssV4_0

{'score': 2.3, 'vector': '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'}


Subscriptions

Temporal Temporal-proxy
cve-icon MITRE

Status: PUBLISHED

Assigner: Temporal

Published:

Updated: 2026-11-18T21:16:56.903Z

Reserved: 2026-11-18T17:26:17.952Z

Link: CVE-2026-132559

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-18T21:17:57.357

Modified: 2026-11-18T22:17:20.777

Link: CVE-2026-132559

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-18T21:45:02Z

Weaknesses