{"api_version":"1","generated_at":"2026-11-20T19:24:18+00:00","cve":"CVE-2026-130091","urls":{"html":"https://cve.report/CVE-2026-130091","api":"https://cve.report/api/cve/CVE-2026-130091.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-130091","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-130091"},"summary":{"title":"temporal-proxy can be terminated by memory exhaustion when decompressing stored payloads","description":"A caller with write permission in a namespace can terminate temporal-proxy through memory exhaustion by storing highly compressed payloads in Workflow history, and the stored history causes the same failure on every later read. temporal-proxy 1.2.0 decompresses every payload marked as compressed in the responses it forwards, whether or not compression is configured. Each payload is limited to 4 MiB after decompression, but the total for a response is not, and the decoded payloads are held in memory together. The caller can store many small, highly compressed payloads through the proxy or directly at the upstream Temporal service. When that history is read through the proxy, for example by a Worker processing a task, the proxy can run out of memory and be terminated. The codec server's /decode endpoint is affected in the same way when it is enabled. Only temporal-proxy 1.2.0 is affected; earlier versions do not decompress payloads. The issue is fixed in 1.2.1. Upgrade to 1.2.1 or later.","state":"PUBLISHED","assigner":"Temporal","published_at":"2026-11-18 21:17:49","updated_at":"2026-11-18 22:17:18"},"problem_types":["CWE-409","CWE-409 CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)"],"metrics":[{"version":"4.0","source":"security@temporal.io","type":"Secondary","score":"7.1","severity":"HIGH","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/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:N/PR:L/UI:N/VC:N/VI:N/VA:H/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":7.1,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"NONE","vulnIntegrityImpact":"NONE","vulnAvailabilityImpact":"HIGH","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":"7.1","severity":"HIGH","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","data":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"NETWORK","baseScore":7.1,"baseSeverity":"HIGH","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:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"HIGH","vulnConfidentialityImpact":"NONE","vulnIntegrityImpact":"NONE","vulnerabilityResponseEffort":"NOT_DEFINED"}}],"references":[{"url":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/codec.go#L157-L166","name":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/codec.go#L157-L166","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/5c5060cc77c8e94a01de1414cc32e55751580381","name":"https://github.com/temporalio/temporal-proxy/commit/5c5060cc77c8e94a01de1414cc32e55751580381","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/compressor.go#L206-L262","name":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/compressor.go#L206-L262","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/commit/ea70ede864cdf6aa9591432d0464a6d6f3413260","name":"https://github.com/temporalio/temporal-proxy/commit/ea70ede864cdf6aa9591432d0464a6d6f3413260","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/295","name":"https://github.com/temporalio/temporal-proxy/pull/295","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/301","name":"https://github.com/temporalio/temporal-proxy/pull/301","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-130091","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-130091","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"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.2.1 or later. Fixed releases limit the bytes decoded for one response to its upstream's maxResponseSize, and the bytes held at once across every response and codec server request to compression.maxDecodedInFlight, 512 MiB by default; a response that would exceed either limit is refused with ResourceExhausted. A configuration whose maxResponseSize exceeds compression.maxDecodedInFlight must raise compression.maxDecodedInFlight to match, or the proxy does not start.","time":"","lang":"en"}],"workarounds":[{"source":"CNA","title":"","value":"No setting disables the decoder in 1.2.0. A deployment that has not enabled compression can run 1.1.2 on the 1.1 release line, which does not decompress payloads; one that enabled compression on 1.2.0 cannot, because 1.1 passes the stored compressed payloads to clients undecoded. Deleting the Workflow Executions that hold the payloads stops the repeated failures; terminating or resetting them does not remove the history.","time":"","lang":"en"}],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"130091","cve":"CVE-2026-130091","epss":"0.004720000","percentile":"0.415610000","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-130091","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-11-18T21:19:00.476228Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-11-18T21:19:07.877Z","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/compressor.go","internal/proxy/compression.go","internal/proxy/codec.go"],"programRoutines":[{"name":"Compressor.Decode"},{"name":"NewCodecs"}],"repo":"https://github.com/temporalio/temporal-proxy","vendor":"Temporal Technologies, Inc.","versions":[{"lessThan":"1.2.1","status":"affected","version":"1.2.0","versionType":"semver"}]}],"configurations":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>Every temporal-proxy 1.2.0 deployment is affected; no compression, encryption, or codec server setting is required. The attacker needs write permission in one namespace whose history is read through the proxy.</p>"}],"value":"Every temporal-proxy 1.2.0 deployment is affected; no compression, encryption, or codec server setting is required. The attacker needs write permission in one namespace whose history is read through the proxy."},{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>The Subsequent System Availability metric is None because the upstream Temporal service keeps running and serving clients that do not use the proxy; loss of the proxy's own service is scored as Vulnerable System Availability.</p>"}],"value":"The Subsequent System Availability metric is None because the upstream Temporal service keeps running and serving clients that do not use the proxy; loss of the proxy's own service is scored as Vulnerable System Availability."}],"descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>A caller with write permission in a namespace can terminate temporal-proxy through memory exhaustion by storing highly compressed payloads in Workflow history, and the stored history causes the same failure on every later read. temporal-proxy 1.2.0 decompresses every payload marked as compressed in the responses it forwards, whether or not compression is configured. Each payload is limited to 4 MiB after decompression, but the total for a response is not, and the decoded payloads are held in memory together. The caller can store many small, highly compressed payloads through the proxy or directly at the upstream Temporal service. When that history is read through the proxy, for example by a Worker processing a task, the proxy can run out of memory and be terminated. The codec server's /decode endpoint is affected in the same way when it is enabled. Only temporal-proxy 1.2.0 is affected; earlier versions do not decompress payloads. The issue is fixed in 1.2.1. Upgrade to 1.2.1 or later.</p>"}],"value":"A caller with write permission in a namespace can terminate temporal-proxy through memory exhaustion by storing highly compressed payloads in Workflow history, and the stored history causes the same failure on every later read. temporal-proxy 1.2.0 decompresses every payload marked as compressed in the responses it forwards, whether or not compression is configured. Each payload is limited to 4 MiB after decompression, but the total for a response is not, and the decoded payloads are held in memory together. The caller can store many small, highly compressed payloads through the proxy or directly at the upstream Temporal service. When that history is read through the proxy, for example by a Worker processing a task, the proxy can run out of memory and be terminated. The codec server's /decode endpoint is affected in the same way when it is enabled. Only temporal-proxy 1.2.0 is affected; earlier versions do not decompress payloads. The issue is fixed in 1.2.1. Upgrade to 1.2.1 or later."}],"impacts":[{"descriptions":[{"lang":"en","value":"Termination of the proxy process through memory exhaustion, interrupting service for every namespace and upstream it serves. Restarting the proxy does not restore service while the stored payloads remain. No confidentiality or integrity impact was identified."}]}],"metrics":[{"cvssV4_0":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"NETWORK","baseScore":7.1,"baseSeverity":"HIGH","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:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"HIGH","vulnConfidentialityImpact":"NONE","vulnIntegrityImpact":"NONE","vulnerabilityResponseEffort":"NOT_DEFINED"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-409","description":"CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-18T20:24:35.307Z","orgId":"61241ed8-fa44-4f23-92db-b8c443751968","shortName":"Temporal"},"references":[{"name":"Inbound codec chain in temporal-proxy 1.2.0, which always includes the decompressor","tags":["product"],"url":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/codec.go#L157-L166"},{"name":"Compressor.Decode in temporal-proxy 1.2.0, which bounds each payload but not the response","tags":["product"],"url":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/compressor.go#L206-L262"},{"name":"Fix pull request","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/295"},{"name":"Fix commit","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/ea70ede864cdf6aa9591432d0464a6d6f3413260"},{"name":"Backport pull request for the 1.2 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/301"},{"name":"Backport commit on releases/v1.2.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/5c5060cc77c8e94a01de1414cc32e55751580381"},{"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.2.1 or later. Fixed releases limit the bytes decoded for one response to its upstream's maxResponseSize, and the bytes held at once across every response and codec server request to compression.maxDecodedInFlight, 512 MiB by default; a response that would exceed either limit is refused with ResourceExhausted. A configuration whose maxResponseSize exceeds compression.maxDecodedInFlight must raise compression.maxDecodedInFlight to match, or the proxy does not start.</p>"}],"value":"Upgrade to temporal-proxy 1.2.1 or later. Fixed releases limit the bytes decoded for one response to its upstream's maxResponseSize, and the bytes held at once across every response and codec server request to compression.maxDecodedInFlight, 512 MiB by default; a response that would exceed either limit is refused with ResourceExhausted. A configuration whose maxResponseSize exceeds compression.maxDecodedInFlight must raise compression.maxDecodedInFlight to match, or the proxy does not start."}],"source":{"discovery":"INTERNAL"},"title":"temporal-proxy can be terminated by memory exhaustion when decompressing stored payloads","workarounds":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>No setting disables the decoder in 1.2.0. A deployment that has not enabled compression can run 1.1.2 on the 1.1 release line, which does not decompress payloads; one that enabled compression on 1.2.0 cannot, because 1.1 passes the stored compressed payloads to clients undecoded. Deleting the Workflow Executions that hold the payloads stops the repeated failures; terminating or resetting them does not remove the history.</p>"}],"value":"No setting disables the decoder in 1.2.0. A deployment that has not enabled compression can run 1.1.2 on the 1.1 release line, which does not decompress payloads; one that enabled compression on 1.2.0 cannot, because 1.1 passes the stored compressed payloads to clients undecoded. Deleting the Workflow Executions that hold the payloads stops the repeated failures; terminating or resetting them does not remove the history."}]}},"cveMetadata":{"assignerOrgId":"61241ed8-fa44-4f23-92db-b8c443751968","assignerShortName":"Temporal","cveId":"CVE-2026-130091","datePublished":"2026-11-18T20:24:35.307Z","dateReserved":"2026-11-16T20:59:59.874Z","dateUpdated":"2026-11-18T21:19:07.877Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-18 21:17:49","lastModifiedDate":"2026-11-18 22:17:18","problem_types":["CWE-409","CWE-409 CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)"],"metrics":{"cvssMetricV40":[{"source":"security@temporal.io","type":"Secondary","cvssData":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/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":7.1,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"NONE","vulnIntegrityImpact":"NONE","vulnAvailabilityImpact":"HIGH","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:19:00.476228Z","id":"CVE-2026-130091","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"130091","Ordinal":"1","Title":"temporal-proxy can be terminated by memory exhaustion when decom","CVE":"CVE-2026-130091","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"130091","Ordinal":"1","NoteData":"A caller with write permission in a namespace can terminate temporal-proxy through memory exhaustion by storing highly compressed payloads in Workflow history, and the stored history causes the same failure on every later read. temporal-proxy 1.2.0 decompresses every payload marked as compressed in the responses it forwards, whether or not compression is configured. Each payload is limited to 4 MiB after decompression, but the total for a response is not, and the decoded payloads are held in memory together. The caller can store many small, highly compressed payloads through the proxy or directly at the upstream Temporal service. When that history is read through the proxy, for example by a Worker processing a task, the proxy can run out of memory and be terminated. The codec server's /decode endpoint is affected in the same way when it is enabled. Only temporal-proxy 1.2.0 is affected; earlier versions do not decompress payloads. The issue is fixed in 1.2.1. Upgrade to 1.2.1 or later.","Type":"Description","Title":"temporal-proxy can be terminated by memory exhaustion when decom"}]}}}