GHSA-JJW4-5PWX-3WQ5
Vulnerability from github – Published: 2026-11-18 21:31 – Updated: 2026-11-18 21:31When 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.
{
"affected": [],
"aliases": [
"CVE-2026-132559"
],
"database_specific": {
"cwe_ids": [
"CWE-212"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-18T21:17:57Z",
"severity": "LOW"
},
"details": "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\u0027s history at the upstream can read them. When the proxy returns a failure to a Worker, it decrypts the failure\u0027s 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.",
"id": "GHSA-jjw4-5pwx-3wq5",
"modified": "2026-11-18T21:31:40Z",
"published": "2026-11-18T21:31:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-132559"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/pull/308"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/pull/307"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/pull/306"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/pull/305"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/pull/304"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/pull/303"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/pull/302"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/pull/296"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/commit/ea541ae21fbfda65bd867a88020ddfce0b92c907"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/commit/c5d211cda68a7c07ec691b3b47f1c0ab6fc495fb"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/commit/95b99dceaa1a19c666b1661e2edef4090acda119"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/commit/8bd1045ccfaaa54580444dd9855fd87f3b1b252b"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/commit/85492b5728362d8fd082e5cff9290a23c016ae30"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/commit/7742a645c526dde4b6a182e6e55e2f9d9ea2b43b"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/commit/68dea481cdd8112432d5efb495b0963e03fff14d"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/commit/53710919feb8af12e2f4b789e2d997a412cdd33f"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L55-L70"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1"
},
{
"type": "WEB",
"url": "https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L26-L29"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "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",
"type": "CVSS_V4"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.