Analysis and contextual insights are available on OpenCVE Cloud.
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.
No advisories yet.
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
Status: PUBLISHED
Assigner: Temporal
Published:
Updated: 2026-11-18T21:16:56.903Z
Reserved: 2026-11-18T17:26:17.952Z
Link: CVE-2026-132559
No data.
Status : Received
Published: 2026-11-18T21:17:57.357
Modified: 2026-11-18T22:17:20.777
Link: CVE-2026-132559
No data.
OpenCVE Enrichment
Updated: 2026-11-18T21:45:02Z