temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext
Summary
| CVE | CVE-2026-132559 |
|---|---|
| State | PUBLISHED |
| Assigner | Temporal |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-18 21:17:57 UTC |
| Updated | 2026-11-18 22:17:20 UTC |
| 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. |
Risk And Classification
Primary CVSS: v4.0 2.3 LOW from [email protected]
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS: 0.004830000 probability, percentile 0.424310000 (date 2026-11-19)
Problem Types: CWE-212 | CWE-212 CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 4.0 | [email protected] | Secondary | 2.3 | LOW | 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/E:X/C... |
| 4.0 | CNA | CVSS | 2.3 | LOW | 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 |
CVSS v4.0 Breakdown
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Temporal Technologies Inc. | Temporal-proxy | affected 0.9.0 0.10.1 semver | Not specified |
| CNA | Temporal Technologies Inc. | Temporal-proxy | affected 1.0.0 1.0.2 semver | Not specified |
| CNA | Temporal Technologies Inc. | Temporal-proxy | affected 1.1.0 1.1.2 semver | Not specified |
| CNA | Temporal Technologies Inc. | Temporal-proxy | affected 1.2.0 1.2.1 semver | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/temporalio/temporal-proxy/commit/ea541ae21fbfda65bd867a88020d... | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/pull/296 | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/pull/302 | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/pull/304 | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/commit/85492b5728362d8fd082e5cff929... | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/commit/7742a645c526dde4b6a182e6e55e... | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/pull/306 | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/pull/307 | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/releases/tag/v1.2.1 | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/pull/308 | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/pull/305 | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/commit/c5d211cda68a7c07ec691b3b47f1... | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/releases/tag/v1.1.2 | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/commit/8bd1045ccfaaa54580444dd9855f... | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/pull/303 | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/commit/68dea481cdd8112432d5efb495b0... | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/releases/tag/v1.0.2 | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/commit/95b99dceaa1a19c666b1661e2ede... | [email protected] | github.com | |
| github.com/temporalio/temporal-proxy/commit/53710919feb8af12e2f4b789e2d9... | [email protected] | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: An external security researcher who reported this issue responsibly to Temporal Technologies (en)
Additional Advisory Data
Solutions
CNA: 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.
Workarounds
CNA: 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.