CVE-2026-132559 temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext
- Exploited in the wild
- Not known
- Fix
- 1.0.2, 1.1.2, 1.2.1, 1.0.0
What is CVE-2026-132559?
CVE-2026-132559 is a low-severity vulnerability in temporal-proxy, published on 18 Nov 2026.
Official 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
Which versions are affected by CVE-2026-132559?
How do I fix CVE-2026-132559?
Upgrade temporal-proxy to the fixed version for your release line. The advisory names 1.0.2, 1.1.2, 1.2.1 and 1.0.0.
Is CVE-2026-132559 being exploited?
There is no known exploitation of CVE-2026-132559 in the wild and no public exploit code.
Sources
Also known as GHSA-jjw4-5pwx-3wq5.