CVE-2026-132559
Last modified
CVE-2026-132559 is a low-severity vulnerability rated 2.3/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Temporal Technologies, Inc. | temporal-proxy | >= 0.9.0, <= 0.10.1; >= 1.0.0, < 1.0.2; >= 1.1.0, < 1.1.2; >= 1.2.0, < 1.2.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-132559?
How severe is CVE-2026-132559?
How do I fix CVE-2026-132559?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-13249An unauthenticated Remote Code Execution via Arbitrary File …9.8
- CVE-2026-1325A security flaw has been discovered in Sangfor Operation and…9.8
- CVE-2026-13250The Solace Extra plugin for WordPress is vulnerable to autho…5.3
- CVE-2026-13251The Perfmatters plugin for WordPress is vulnerable to Direct…7.5
- CVE-2026-13252The RSS Aggregator by Feedzy – Feed to Post, Autoblogging, N…6.4
- CVE-2026-13253The Ultimate Post plugin for WordPress is vulnerable to Stor…6.4
- CVE-2026-132560A flaw has been found in MemTensor memmy-agent up to 1.1.1. …3.3
- CVE-2026-13257IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.1 thr…6.5
- CVE-2026-13258IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.1 thr…5.4
- CVE-2026-1326A weakness has been identified in Totolink NR1800X 9.1.0u.62…8.8
- CVE-2026-13260IBM Verify Identity Access could allow a remote attacker to …7.5
- CVE-2026-132600The Mail Mint – Email Marketing, Automation & WooCommerce Em…6.4
Are you affected by CVE-2026-132559?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
