{"api_version":"1","generated_at":"2026-11-20T19:24:19+00:00","cve":"CVE-2026-132559","urls":{"html":"https://cve.report/CVE-2026-132559","api":"https://cve.report/api/cve/CVE-2026-132559.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-132559","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-132559"},"summary":{"title":"temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext","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.","state":"PUBLISHED","assigner":"Temporal","published_at":"2026-11-18 21:17:57","updated_at":"2026-11-18 22:17:20"},"problem_types":["CWE-212","CWE-212 CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer"],"metrics":[{"version":"4.0","source":"security@temporal.io","type":"Secondary","score":"2.3","severity":"LOW","vector":"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","data":{"version":"4.0","vectorString":"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","baseScore":2.3,"baseSeverity":"LOW","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"PRESENT","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"NONE","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}},{"version":"4.0","source":"CNA","type":"CVSS","score":"2.3","severity":"LOW","vector":"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","data":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"PRESENT","attackVector":"NETWORK","baseScore":2.3,"baseSeverity":"LOW","exploitMaturity":"NOT_DEFINED","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"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","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"NONE","vulnerabilityResponseEffort":"NOT_DEFINED"}}],"references":[{"url":"https://github.com/temporalio/temporal-proxy/commit/ea541ae21fbfda65bd867a88020ddfce0b92c907","name":"https://github.com/temporalio/temporal-proxy/commit/ea541ae21fbfda65bd867a88020ddfce0b92c907","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/296","name":"https://github.com/temporalio/temporal-proxy/pull/296","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/302","name":"https://github.com/temporalio/temporal-proxy/pull/302","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/304","name":"https://github.com/temporalio/temporal-proxy/pull/304","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/85492b5728362d8fd082e5cff9290a23c016ae30","name":"https://github.com/temporalio/temporal-proxy/commit/85492b5728362d8fd082e5cff9290a23c016ae30","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/7742a645c526dde4b6a182e6e55e2f9d9ea2b43b","name":"https://github.com/temporalio/temporal-proxy/commit/7742a645c526dde4b6a182e6e55e2f9d9ea2b43b","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L55-L70","name":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L55-L70","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/306","name":"https://github.com/temporalio/temporal-proxy/pull/306","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/307","name":"https://github.com/temporalio/temporal-proxy/pull/307","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1","name":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/308","name":"https://github.com/temporalio/temporal-proxy/pull/308","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/305","name":"https://github.com/temporalio/temporal-proxy/pull/305","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/c5d211cda68a7c07ec691b3b47f1c0ab6fc495fb","name":"https://github.com/temporalio/temporal-proxy/commit/c5d211cda68a7c07ec691b3b47f1c0ab6fc495fb","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2","name":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/8bd1045ccfaaa54580444dd9855fd87f3b1b252b","name":"https://github.com/temporalio/temporal-proxy/commit/8bd1045ccfaaa54580444dd9855fd87f3b1b252b","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/303","name":"https://github.com/temporalio/temporal-proxy/pull/303","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/68dea481cdd8112432d5efb495b0963e03fff14d","name":"https://github.com/temporalio/temporal-proxy/commit/68dea481cdd8112432d5efb495b0963e03fff14d","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2","name":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L26-L29","name":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L26-L29","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/95b99dceaa1a19c666b1661e2edef4090acda119","name":"https://github.com/temporalio/temporal-proxy/commit/95b99dceaa1a19c666b1661e2edef4090acda119","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/53710919feb8af12e2f4b789e2d997a412cdd33f","name":"https://github.com/temporalio/temporal-proxy/commit/53710919feb8af12e2f4b789e2d997a412cdd33f","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-132559","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-132559","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Temporal Technologies, Inc.","product":"temporal-proxy","version":"affected 0.9.0 0.10.1 semver","platforms":[]},{"source":"CNA","vendor":"Temporal Technologies, Inc.","product":"temporal-proxy","version":"affected 1.0.0 1.0.2 semver","platforms":[]},{"source":"CNA","vendor":"Temporal Technologies, Inc.","product":"temporal-proxy","version":"affected 1.1.0 1.1.2 semver","platforms":[]},{"source":"CNA","vendor":"Temporal Technologies, Inc.","product":"temporal-proxy","version":"affected 1.2.0 1.2.1 semver","platforms":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"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.","time":"","lang":"en"}],"workarounds":[{"source":"CNA","title":"","value":"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.","time":"","lang":"en"}],"exploits":[],"credits":[{"source":"CNA","value":"An external security researcher who reported this issue responsibly to Temporal Technologies","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"132559","cve":"CVE-2026-132559","epss":"0.004830000","percentile":"0.424310000","score_date":"2026-11-19","updated_at":"2026-11-20 00:07:18"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-132559","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-11-18T21:16:48.898262Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-11-18T21:16:56.903Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"collectionURL":"https://pkg.go.dev","defaultStatus":"unaffected","packageName":"github.com/temporalio/temporal-proxy","product":"temporal-proxy","programFiles":["pkg/codec/failure.go","internal/proxy/codec.go"],"programRoutines":[{"name":"EncodeFailure"},{"name":"RestoreFailure"},{"name":"NewCodecs"},{"name":"Codecs.Interceptor"}],"repo":"https://github.com/temporalio/temporal-proxy","vendor":"Temporal Technologies, Inc.","versions":[{"lessThanOrEqual":"0.10.1","status":"affected","version":"0.9.0","versionType":"semver"},{"lessThan":"1.0.2","status":"affected","version":"1.0.0","versionType":"semver"},{"lessThan":"1.1.2","status":"affected","version":"1.1.0","versionType":"semver"},{"lessThan":"1.2.1","status":"affected","version":"1.2.0","versionType":"semver"}]}],"configurations":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>Exposure requires all of the following. Payload encryption is enabled; it is off by default. Failure text is moved into encoded attributes, either by the proxy (encryption.failures) or by the SDK, for example the Go SDK's EncodeCommonAttributes option. A Worker sends back a failure it received through the proxy. The reader can read Workflow history at the upstream Temporal service without going through the proxy, for example a user with read access to the namespace, the upstream's operator, or anyone with access to its storage.</p>"}],"value":"Exposure requires all of the following. Payload encryption is enabled; it is off by default. Failure text is moved into encoded attributes, either by the proxy (encryption.failures) or by the SDK, for example the Go SDK's EncodeCommonAttributes option. A Worker sends back a failure it received through the proxy. The reader can read Workflow history at the upstream Temporal service without going through the proxy, for example a user with read access to the namespace, the upstream's operator, or anyone with access to its storage."},{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>The Attack Requirements metric is Present because the exposure depends on the encryption configuration and on Worker code sending back a received failure, neither of which the reader controls. Confidentiality is Low because only failure messages and stack traces are exposed, the reader does not choose which, and payloads stay encrypted.</p>"}],"value":"The Attack Requirements metric is Present because the exposure depends on the encryption configuration and on Worker code sending back a received failure, neither of which the reader controls. Confidentiality is Low because only failure messages and stack traces are exposed, the reader does not choose which, and payloads stay encrypted."}],"credits":[{"lang":"en","type":"finder","value":"An external security researcher who reported this issue responsibly to Temporal Technologies"}],"descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>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.</p>"}],"value":"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."}],"impacts":[{"descriptions":[{"lang":"en","value":"Disclosure of failure messages and stack traces, which the deployment encrypts to keep them from the upstream Temporal service, to anyone who can read Workflow history there. Payloads remain encrypted. Failure text the upstream has already stored in plaintext stays readable after upgrading, until the namespace's retention period expires. No integrity or availability impact was identified."}]}],"metrics":[{"cvssV4_0":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"PRESENT","attackVector":"NETWORK","baseScore":2.3,"baseSeverity":"LOW","exploitMaturity":"NOT_DEFINED","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"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","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"NONE","vulnerabilityResponseEffort":"NOT_DEFINED"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-212","description":"CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-18T20:30:01.372Z","orgId":"61241ed8-fa44-4f23-92db-b8c443751968","shortName":"Temporal"},"references":[{"name":"EncodeFailure in temporal-proxy 1.2.0, which leaves a failure that already has encoded attributes unchanged","tags":["product"],"url":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L26-L29"},{"name":"RestoreFailure in temporal-proxy 1.2.0, which copies the decrypted text back onto the failure","tags":["product"],"url":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L55-L70"},{"name":"Fix pull request","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/296"},{"name":"Fix commit","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/68dea481cdd8112432d5efb495b0963e03fff14d"},{"name":"Follow-up fix pull request","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/305"},{"name":"Follow-up fix commit","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/53710919feb8af12e2f4b789e2d997a412cdd33f"},{"name":"Backport pull request for the 1.0 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/304"},{"name":"Backport commit on releases/v1.0.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/95b99dceaa1a19c666b1661e2edef4090acda119"},{"name":"Follow-up backport pull request for the 1.0 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/308"},{"name":"Follow-up backport commit on releases/v1.0.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/85492b5728362d8fd082e5cff9290a23c016ae30"},{"name":"Backport pull request for the 1.1 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/303"},{"name":"Backport commit on releases/v1.1.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/8bd1045ccfaaa54580444dd9855fd87f3b1b252b"},{"name":"Follow-up backport pull request for the 1.1 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/307"},{"name":"Follow-up backport commit on releases/v1.1.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/7742a645c526dde4b6a182e6e55e2f9d9ea2b43b"},{"name":"Backport pull request for the 1.2 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/302"},{"name":"Backport commit on releases/v1.2.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/c5d211cda68a7c07ec691b3b47f1c0ab6fc495fb"},{"name":"Follow-up backport pull request for the 1.2 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/306"},{"name":"Follow-up backport commit on releases/v1.2.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/ea541ae21fbfda65bd867a88020ddfce0b92c907"},{"name":"temporal-proxy 1.0.2","tags":["release-notes"],"url":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2"},{"name":"temporal-proxy 1.1.2","tags":["release-notes"],"url":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2"},{"name":"temporal-proxy 1.2.1","tags":["release-notes"],"url":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1"}],"solutions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>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.</p>"}],"value":"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."}],"source":{"discovery":"EXTERNAL"},"title":"temporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintext","workarounds":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>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.</p>"}],"value":"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."}]}},"cveMetadata":{"assignerOrgId":"61241ed8-fa44-4f23-92db-b8c443751968","assignerShortName":"Temporal","cveId":"CVE-2026-132559","datePublished":"2026-11-18T20:30:01.372Z","dateReserved":"2026-11-18T17:26:17.952Z","dateUpdated":"2026-11-18T21:16:56.903Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-18 21:17:57","lastModifiedDate":"2026-11-18 22:17:20","problem_types":["CWE-212","CWE-212 CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer"],"metrics":{"cvssMetricV40":[{"source":"security@temporal.io","type":"Secondary","cvssData":{"version":"4.0","vectorString":"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","baseScore":2.3,"baseSeverity":"LOW","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"PRESENT","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"NONE","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-11-18T21:16:48.898262Z","id":"CVE-2026-132559","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"132559","Ordinal":"1","Title":"temporal-proxy can send decrypted failure messages and stack tra","CVE":"CVE-2026-132559","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"132559","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"temporal-proxy can send decrypted failure messages and stack tra"}]}}}