{"api_version":"1","generated_at":"2026-11-20T19:24:18+00:00","cve":"CVE-2026-130090","urls":{"html":"https://cve.report/CVE-2026-130090","api":"https://cve.report/api/cve/CVE-2026-130090.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-130090","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-130090"},"summary":{"title":"temporal-proxy can send a request under another upstream's credential when templated upstreams render the same address","description":"When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream's credential, namespace translation, and payload encryption keys. temporal-proxy pools connections for templated upstreams by rendered address and TLS server name only, although each upstream's outbound credential, namespace translation, and payload encryption keys, where configured, are attached to its connection. A request routed to one upstream can therefore be sent over the connection the other created, and the upstream Temporal service authorizes it as the other upstream's principal. Configuration validation rejects only identical hostPort values, so templates that differ in text but render the same address are accepted. This mixes the two upstreams' ordinary traffic, and a caller that an external authenticator restricts to one upstream's namespaces can use it to act under the other upstream's credential. Deployments with at most one templated upstream are not affected. temporal-proxy versions 0.1.0 through 1.1.1 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.0, 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:49","updated_at":"2026-11-18 22:17:18"},"problem_types":["CWE-488","CWE-488 CWE-488: Exposure of Data Element to Wrong Session"],"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:L/VA:N/SC:L/SI:L/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:L/VA:N/SC:L/SI:L/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":"LOW","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"LOW","subIntegrityImpact":"LOW","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:L/VA:N/SC:L/SI:L/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":"LOW","subIntegrityImpact":"LOW","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"LOW","vulnerabilityResponseEffort":"NOT_DEFINED"}}],"references":[{"url":"https://github.com/temporalio/temporal-proxy/pull/285","name":"https://github.com/temporalio/temporal-proxy/pull/285","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/9d1dc1dcf92fef191e61e9076ff46fd7c8570702","name":"https://github.com/temporalio/temporal-proxy/commit/9d1dc1dcf92fef191e61e9076ff46fd7c8570702","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.0","name":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.0","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/d7228fac60798e4047e00606b8b41573ab2f77c4","name":"https://github.com/temporalio/temporal-proxy/commit/d7228fac60798e4047e00606b8b41573ab2f77c4","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/pull/279","name":"https://github.com/temporalio/temporal-proxy/pull/279","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/commit/d201e99150e90e34b033480f91022067f39b3c8e","name":"https://github.com/temporalio/temporal-proxy/commit/d201e99150e90e34b033480f91022067f39b3c8e","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/286","name":"https://github.com/temporalio/temporal-proxy/pull/286","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-130090","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-130090","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Temporal Technologies, Inc.","product":"temporal-proxy","version":"affected 0.1.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":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"Upgrade to temporal-proxy 1.2.0 or later, or to 1.0.2 or 1.1.2 on those release lines. Fixed releases scope each pooled connection to the upstream that created it. Releases before 1.0.0 receive no fix.","time":"","lang":"en"}],"workarounds":[{"source":"CNA","title":"","value":"Configure templated upstreams so that no two can render the same address, for example by giving each hostPort template a distinct fixed suffix.","time":"","lang":"en"}],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"130090","cve":"CVE-2026-130090","epss":"0.004530000","percentile":"0.400930000","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-130090","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-11-18T21:18:05.592250Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-11-18T21:18:15.630Z","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":["internal/proxy/resolver.go","internal/transport/connect/pool.go"],"programRoutines":[{"name":"DynamicResolver.Resolve"},{"name":"Pool.ConnOrCreate"}],"repo":"https://github.com/temporalio/temporal-proxy","vendor":"Temporal Technologies, Inc.","versions":[{"lessThanOrEqual":"0.10.1","status":"affected","version":"0.1.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"}]}],"configurations":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>Exploitation requires two or more templated upstreams that can render the same address and TLS server name with different outbound credentials, namespace translation, or encryption keys. It crosses an authorization boundary only where an external authenticator restricts callers to particular namespaces; otherwise any caller can already route requests to either upstream.</p>"}],"value":"Exploitation requires two or more templated upstreams that can render the same address and TLS server name with different outbound credentials, namespace translation, or encryption keys. It crosses an authorization boundary only where an external authenticator restricts callers to particular namespaces; otherwise any caller can already route requests to either upstream."},{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>Attack Requirements is Present because the colliding upstream configuration, a restricting external authenticator, and a connection already opened by the other upstream's traffic are outside the caller's control. Confidentiality and integrity are Low on the proxy and on the upstream Temporal service because the caller does not choose which upstream's connection serves the request.</p>"}],"value":"Attack Requirements is Present because the colliding upstream configuration, a restricting external authenticator, and a connection already opened by the other upstream's traffic are outside the caller's control. Confidentiality and integrity are Low on the proxy and on the upstream Temporal service because the caller does not choose which upstream's connection serves the request."}],"descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream's credential, namespace translation, and payload encryption keys. temporal-proxy pools connections for templated upstreams by rendered address and TLS server name only, although each upstream's outbound credential, namespace translation, and payload encryption keys, where configured, are attached to its connection. A request routed to one upstream can therefore be sent over the connection the other created, and the upstream Temporal service authorizes it as the other upstream's principal. Configuration validation rejects only identical hostPort values, so templates that differ in text but render the same address are accepted. This mixes the two upstreams' ordinary traffic, and a caller that an external authenticator restricts to one upstream's namespaces can use it to act under the other upstream's credential. Deployments with at most one templated upstream are not affected. temporal-proxy versions 0.1.0 through 1.1.1 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.0, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line.</p>"}],"value":"When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream's credential, namespace translation, and payload encryption keys. temporal-proxy pools connections for templated upstreams by rendered address and TLS server name only, although each upstream's outbound credential, namespace translation, and payload encryption keys, where configured, are attached to its connection. A request routed to one upstream can therefore be sent over the connection the other created, and the upstream Temporal service authorizes it as the other upstream's principal. Configuration validation rejects only identical hostPort values, so templates that differ in text but render the same address are accepted. This mixes the two upstreams' ordinary traffic, and a caller that an external authenticator restricts to one upstream's namespaces can use it to act under the other upstream's credential. Deployments with at most one templated upstream are not affected. temporal-proxy versions 0.1.0 through 1.1.1 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.0, 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":"Requests routed to one upstream can be authorized at the Temporal server under another upstream's credential, and their payloads encrypted or decrypted under that upstream's keys. The caller does not choose which upstream's connection is used and does not obtain the credential. No 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":"LOW","subIntegrityImpact":"LOW","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"LOW","vulnerabilityResponseEffort":"NOT_DEFINED"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-488","description":"CWE-488: Exposure of Data Element to Wrong Session","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-18T20:28:53.871Z","orgId":"61241ed8-fa44-4f23-92db-b8c443751968","shortName":"Temporal"},"references":[{"name":"Fix pull request","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/279"},{"name":"Fix commit","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/d7228fac60798e4047e00606b8b41573ab2f77c4"},{"name":"Backport pull request for the 1.0 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/286"},{"name":"Backport commit on releases/v1.0.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/9d1dc1dcf92fef191e61e9076ff46fd7c8570702"},{"name":"Backport pull request for the 1.1 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/285"},{"name":"Backport commit on releases/v1.1.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/d201e99150e90e34b033480f91022067f39b3c8e"},{"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.0","tags":["release-notes"],"url":"https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.0"}],"solutions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>Upgrade to temporal-proxy 1.2.0 or later, or to 1.0.2 or 1.1.2 on those release lines. Fixed releases scope each pooled connection to the upstream that created it. Releases before 1.0.0 receive no fix.</p>"}],"value":"Upgrade to temporal-proxy 1.2.0 or later, or to 1.0.2 or 1.1.2 on those release lines. Fixed releases scope each pooled connection to the upstream that created it. Releases before 1.0.0 receive no fix."}],"source":{"discovery":"INTERNAL"},"title":"temporal-proxy can send a request under another upstream's credential when templated upstreams render the same address","workarounds":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>Configure templated upstreams so that no two can render the same address, for example by giving each hostPort template a distinct fixed suffix.</p>"}],"value":"Configure templated upstreams so that no two can render the same address, for example by giving each hostPort template a distinct fixed suffix."}]}},"cveMetadata":{"assignerOrgId":"61241ed8-fa44-4f23-92db-b8c443751968","assignerShortName":"Temporal","cveId":"CVE-2026-130090","datePublished":"2026-11-18T20:28:53.871Z","dateReserved":"2026-11-16T20:59:58.726Z","dateUpdated":"2026-11-18T21:18:15.630Z","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-488","CWE-488 CWE-488: Exposure of Data Element to Wrong Session"],"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:L/VA:N/SC:L/SI:L/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":"LOW","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"LOW","subIntegrityImpact":"LOW","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:18:05.592250Z","id":"CVE-2026-130090","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"130090","Ordinal":"1","Title":"temporal-proxy can send a request under another upstream's crede","CVE":"CVE-2026-130090","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"130090","Ordinal":"1","NoteData":"When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream's credential, namespace translation, and payload encryption keys. temporal-proxy pools connections for templated upstreams by rendered address and TLS server name only, although each upstream's outbound credential, namespace translation, and payload encryption keys, where configured, are attached to its connection. A request routed to one upstream can therefore be sent over the connection the other created, and the upstream Temporal service authorizes it as the other upstream's principal. Configuration validation rejects only identical hostPort values, so templates that differ in text but render the same address are accepted. This mixes the two upstreams' ordinary traffic, and a caller that an external authenticator restricts to one upstream's namespaces can use it to act under the other upstream's credential. Deployments with at most one templated upstream are not affected. temporal-proxy versions 0.1.0 through 1.1.1 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.0, 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 a request under another upstream's crede"}]}}}