CVE-2026-132559temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext
- 2.3LowCVSS base score
- 0.48%Exploitation in 30 daysEPSS · top 58% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Temporal
Published
- 1 day later
· 1 day later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| TemporalCNA (assigner) | 4.0 | Low2.3 | 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 |
| NVDNVD · Received | 4.0 | Low2.3 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
- EPSS (exploitation in 30 days)
- 0.48% · top 58% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 2.3.
Affected products
Temporal Technologies, Inc. · temporal-proxy
- affected 0.9.0 – ≤ 0.10.1
- affected 1.0.0 – < 1.0.2
- affected 1.1.0 – < 1.1.2
- affected 1.2.0 – < 1.2.1
What to do
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.
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.
References
References21
- EncodeFailure in temporal-proxy 1.2.0, which leaves a failure that already has encoded attributes unchanged (opens in a new tab)product
- RestoreFailure in temporal-proxy 1.2.0, which copies the decrypted text back onto the failure (opens in a new tab)product
- Fix pull request (opens in a new tab)patch
- Fix commit (opens in a new tab)patch
- Follow-up fix pull request (opens in a new tab)patch
- Follow-up fix commit (opens in a new tab)patch
- Backport pull request for the 1.0 release line (opens in a new tab)patch
- Backport commit on releases/v1.0.x (opens in a new tab)patch
- Follow-up backport pull request for the 1.0 release line (opens in a new tab)patch
- Follow-up backport commit on releases/v1.0.x (opens in a new tab)patch
- Backport pull request for the 1.1 release line (opens in a new tab)patch
- Backport commit on releases/v1.1.x (opens in a new tab)patch
- Follow-up backport pull request for the 1.1 release line (opens in a new tab)patch
- Follow-up backport commit on releases/v1.1.x (opens in a new tab)patch
- Backport pull request for the 1.2 release line (opens in a new tab)patch
- Backport commit on releases/v1.2.x (opens in a new tab)patch
- Follow-up backport pull request for the 1.2 release line (opens in a new tab)patch
- Follow-up backport commit on releases/v1.2.x (opens in a new tab)patch
- temporal-proxy 1.0.2 (opens in a new tab)release-notes
- temporal-proxy 1.1.2 (opens in a new tab)release-notes
- temporal-proxy 1.2.1 (opens in a new tab)release-notes
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-129272 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-132559)Record last updated .