CVE
Temporal Technologies temporal-proxy plaintext exposure of failure data in workflow history
- Exploited
- No known exploitation
- Fix
- Fixed in 1.0.2, 1.1.2, 1.2.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.0.2, 1.1.2, 1.2.1.
Summary
Temporal Technologies' temporal-proxy can store decrypted failure messages and stack traces in plaintext at the upstream Temporal service, where anyone who can read the Workflow's history can see them. A remote attacker with low-privilege access can trigger this by sending a failure back through the proxy, which forwards the restored text unchanged.
Original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects Go packages
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.0.2, 1.1.2, 1.2.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132559 (temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132559 (entry last updated 2026-11-18):
Affected:
- Go package github.com/temporalio/temporal-proxy: from 0.9.0, through 0.10.1; from 1.0.0, fixed in 1.0.2; from 1.1.0, fixed in 1.1.2; from 1.2.0, fixed in 1.2.1
Fixed versions: 1.0.2, 1.1.2, 1.2.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132559 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132559 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/temporalio/temporal-proxy/pull/296
- https://github.com/temporalio/temporal-proxy/commit/68dea481cdd8112432d5efb495b0963e03fff14d
- https://github.com/temporalio/temporal-proxy/pull/305
- https://github.com/temporalio/temporal-proxy/commit/53710919feb8af12e2f4b789e2d997a412cdd33f
- https://github.com/temporalio/temporal-proxy/pull/304
- https://github.com/temporalio/temporal-proxy/commit/95b99dceaa1a19c666b1661e2edef4090acda119
- https://github.com/temporalio/temporal-proxy/pull/308
- https://github.com/temporalio/temporal-proxy/commit/85492b5728362d8fd082e5cff9290a23c016ae30
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132559
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132559"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
From 0.9.0 · through 0.10.1; From 1.0.0 · fixed in 1.0.2; From 1.1.0 · fixed in 1.1.2; From 1.2.0 · fixed in 1.2.1
Evidence 23
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132559
Is CVE-2026-132559 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-132559?
github.com/temporalio/temporal-proxy (Go): from 0.9.0 through 0.10.1; from 1.0.0 before 1.0.2; from 1.1.0 before 1.1.2; from 1.2.0 before 1.2.1.Source: cve.now feed data
How do I fix CVE-2026-132559?
Upgrade to a fixed version: 1.0.2, 1.1.2, 1.2.1.Source: cve.now feed data