CVE-2026-132559
Received Received - Intake

Information Exposure in Temporal Proxy

Vulnerability report for CVE-2026-132559, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: Temporal Technologies Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-18
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
Temporal Technologies, Inc. temporal-proxy From 0.9.0 (inc) to 0.10.1 (inc)
Temporal Technologies, Inc. temporal-proxy From 1.0.0 (inc) to 1.0.2 (exc)
Temporal Technologies, Inc. temporal-proxy From 1.1.0 (inc) to 1.1.2 (exc)
Temporal Technologies, Inc. temporal-proxy From 1.2.0 (inc) to 1.2.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-212 The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves plaintext failure messages and stack traces being exposed in Temporal-proxy deployments with payload encryption enabled. When a failure occurs, the proxy decrypts and copies these details back onto the failure, which are then sent back through the proxy. The upstream service stores this plaintext data alongside encrypted copies, potentially exposing sensitive information to anyone with access to the Workflow's history.

Detection Guidance

To detect this vulnerability, check the version of temporal-proxy running on your system. Vulnerable versions are 0.9.0 through 1.2.0. Run: temporal-proxy --version. If the version falls within this range, the system is affected. Upgrade to versions 1.0.2, 1.1.2, 1.2.1, or later to resolve the issue.

Impact Analysis

If you use Temporal-proxy versions 0.9.0 through 1.2.0 with failure encryption enabled or SDKs encoding failure attributes, sensitive failure details like stack traces and error messages may be exposed in plaintext. This could lead to information disclosure, affecting confidentiality of workflow data.

Compliance Impact

This vulnerability could lead to exposure of sensitive failure messages and stack traces in plaintext, which may violate data protection requirements under GDPR (e.g., Article 32 on security of processing) and HIPAA (e.g., Security Rule on integrity and confidentiality). Unauthorized access to plaintext failure details could result in unauthorized disclosure of personal or protected health information.

Mitigation Strategies

Upgrade temporal-proxy to a fixed version: 1.0.2, 1.1.2, or 1.2.1 depending on your deployed minor release line. Versions before 1.0.0 are not fixed.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-132559. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...