CVE-2026-132559: low-severity vulnerability in temporal-proxy
temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
8Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 2.3epss 0.5%
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:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Affected products
Temporal Technologies, Inc. · temporal-proxyRelated CVEs — temporal-proxy
In the same product, most dangerous first.
CVE-2026-130092HIGHUnauthenticated callers can exhaust temporal-proxy memory through unbounded request metricsEPSS 0.6%CVE-2026-130091HIGHtemporal-proxy can be terminated by memory exhaustion when decompressing stored payloadsEPSS 0.5%CVE-2026-130090LOWtemporal-proxy can send a request under another upstream's credential when templated upstreams render the same addressEPSS 0.5%CVE-2026-108126MEDIUMtemporal-proxy payload decryption is not bound to the request namespaceEPSS 0.4%CVE-2026-130089HIGHtemporal-proxy request namespace can redirect a templated upstream and leak its API keyEPSS 0.3%
References
https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L26-L29https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L55-L70https://github.com/temporalio/temporal-proxy/commit/53710919feb8af12e2f4b789e2d997a412cdd33fhttps://github.com/temporalio/temporal-proxy/commit/68dea481cdd8112432d5efb495b0963e03fff14dhttps://github.com/temporalio/temporal-proxy/commit/7742a645c526dde4b6a182e6e55e2f9d9ea2b43bhttps://github.com/temporalio/temporal-proxy/commit/85492b5728362d8fd082e5cff9290a23c016ae30https://github.com/temporalio/temporal-proxy/commit/8bd1045ccfaaa54580444dd9855fd87f3b1b252bhttps://github.com/temporalio/temporal-proxy/commit/95b99dceaa1a19c666b1661e2edef4090acda119https://github.com/temporalio/temporal-proxy/commit/c5d211cda68a7c07ec691b3b47f1c0ab6fc495fbhttps://github.com/temporalio/temporal-proxy/commit/ea541ae21fbfda65bd867a88020ddfce0b92c907https://github.com/temporalio/temporal-proxy/pull/296https://github.com/temporalio/temporal-proxy/pull/302