# CVE-2026-132559: temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext


- **Severity:** Low 2.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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-jjw4-5pwx-3wq5

## What is CVE-2026-132559?

CVE-2026-132559 is a low-severity vulnerability in temporal-proxy, published on 18 Nov 2026. 

### Official 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.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

## Which versions are affected by CVE-2026-132559?


## How do I fix CVE-2026-132559?

Upgrade temporal-proxy to the fixed version for your release line. The advisory names 1.0.2, 1.1.2, 1.2.1 and 1.0.0.

## Is CVE-2026-132559 being exploited?

There is no known exploitation of CVE-2026-132559 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-132559 and fix it if it is affected.

What it is: CVE-2026-132559 is a low-severity vulnerability in temporal-proxy, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132559 in the wild and no public exploit code.

Affected product: temporal-proxy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-132559/ (Markdown: https://insights.sbomify.com/CVE-2026-132559/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-132559
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-132559
- OSV: https://osv.dev/vulnerability/CVE-2026-132559

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-132559/
Summaries are generated and may contain mistakes; the official description above is the record.
