CVE-2026-132559
temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext
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.
INFO
Published Date :
Nov. 18, 2026, 9:17 p.m.
Last Modified :
Nov. 18, 2026, 10:17 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
Affected Products
The following products are affected by CVE-2026-132559
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 4.0 | LOW | 61241ed8-fa44-4f23-92db-b8c443751968 | ||||
| CVSS 4.0 | LOW | [email protected] |
Solution
- Upgrade temporal-proxy to versions 1.0.2, 1.1.2, or 1.2.1.
- Upgrade to a fixed release for your deployed minor release line.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-132559.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-132559 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-132559
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-132559 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-132559 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Nov. 18, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2026-132559', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-11-18T21:16:48.898262Z'} -
New CVE Received by [email protected]
Nov. 18, 2026
Action Type Old Value New Value 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. Added CVSS V4.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 Added CWE CWE-212 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/132xxx/CVE-2026-132559.json">CVE-2026-132559</a> Added Reference https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L26-L29 Added Reference https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L55-L70 Added Reference https://github.com/temporalio/temporal-proxy/commit/53710919feb8af12e2f4b789e2d997a412cdd33f Added Reference https://github.com/temporalio/temporal-proxy/commit/68dea481cdd8112432d5efb495b0963e03fff14d Added Reference https://github.com/temporalio/temporal-proxy/commit/7742a645c526dde4b6a182e6e55e2f9d9ea2b43b Added Reference https://github.com/temporalio/temporal-proxy/commit/85492b5728362d8fd082e5cff9290a23c016ae30 Added Reference https://github.com/temporalio/temporal-proxy/commit/8bd1045ccfaaa54580444dd9855fd87f3b1b252b Added Reference https://github.com/temporalio/temporal-proxy/commit/95b99dceaa1a19c666b1661e2edef4090acda119 Added Reference https://github.com/temporalio/temporal-proxy/commit/c5d211cda68a7c07ec691b3b47f1c0ab6fc495fb Added Reference https://github.com/temporalio/temporal-proxy/commit/ea541ae21fbfda65bd867a88020ddfce0b92c907 Added Reference https://github.com/temporalio/temporal-proxy/pull/296 Added Reference https://github.com/temporalio/temporal-proxy/pull/302 Added Reference https://github.com/temporalio/temporal-proxy/pull/303 Added Reference https://github.com/temporalio/temporal-proxy/pull/304 Added Reference https://github.com/temporalio/temporal-proxy/pull/305 Added Reference https://github.com/temporalio/temporal-proxy/pull/306 Added Reference https://github.com/temporalio/temporal-proxy/pull/307 Added Reference https://github.com/temporalio/temporal-proxy/pull/308 Added Reference https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2 Added Reference https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2 Added Reference https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1