{"api_version":"1","generated_at":"2026-11-20T19:24:18+00:00","cve":"CVE-2026-130089","urls":{"html":"https://cve.report/CVE-2026-130089","api":"https://cve.report/api/cve/CVE-2026-130089.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-130089","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-130089"},"summary":{"title":"temporal-proxy request namespace can redirect a templated upstream and leak its API key","description":"A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream's hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.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, and rotate any upstream API key that untrusted callers could reach.","state":"PUBLISHED","assigner":"Temporal","published_at":"2026-11-18 21:17:48","updated_at":"2026-11-18 22:17:18"},"problem_types":["CWE-918","CWE-918 CWE-918: Server-Side Request Forgery"],"metrics":[{"version":"4.0","source":"security@temporal.io","type":"Secondary","score":"7.3","severity":"HIGH","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/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:H/VI:N/VA:N/SC:H/SI:H/SA:H/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.3,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"PRESENT","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"NONE","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"HIGH","subIntegrityImpact":"HIGH","subAvailabilityImpact":"HIGH","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.3","severity":"HIGH","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H","data":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"PRESENT","attackVector":"NETWORK","baseScore":7.3,"baseSeverity":"HIGH","exploitMaturity":"NOT_DEFINED","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"HIGH","subConfidentialityImpact":"HIGH","subIntegrityImpact":"HIGH","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"NONE","vulnerabilityResponseEffort":"NOT_DEFINED"}}],"references":[{"url":"https://github.com/temporalio/temporal-proxy/pull/294","name":"https://github.com/temporalio/temporal-proxy/pull/294","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8","name":"https://github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313a","name":"https://github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313a","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90","name":"https://github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/292","name":"https://github.com/temporalio/temporal-proxy/pull/292","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/pull/293","name":"https://github.com/temporalio/temporal-proxy/pull/293","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/cd60785edd81cfa0c599b17f94ee7de7d8eaf061","name":"https://github.com/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061","refsource":"security@temporal.io","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go#L259-L282","name":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go#L259-L282","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/284","name":"https://github.com/temporalio/temporal-proxy/pull/284","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://www.cve.org/CVERecord?id=CVE-2026-130089","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-130089","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":[]},{"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 reject a request whose templated upstream address does not render to a plain host name or IP address with an optional port, or whose templated TLS server name is not a plain host name. They also refuse at configuration load a templated hostPort or tls.serverName whose host does not end in a literal domain, as in {{ .RemoteNamespace }}.tmprl.cloud:7233, so a configuration that templates the whole host must be changed before upgrading. Rotate any upstream API key held by an affected deployment that untrusted callers could reach. Releases before 1.0.0 receive no fix.","time":"","lang":"en"}],"workarounds":[{"source":"CNA","title":"","value":"Use fixed upstream addresses, or routing rules that match literal namespace names, with no default or system route to a templated upstream. Alternatively, set a literal tls.serverName on the templated upstream, or use an external authenticator that admits only listed namespaces.","time":"","lang":"en"}],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"130089","cve":"CVE-2026-130089","epss":"0.003450000","percentile":"0.286790000","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-130089","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-11-18T21:19:48.680937Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-11-18T21:19:56.314Z","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/config/upstream.go"],"programRoutines":[{"name":"DynamicResolver.Resolve"},{"name":"invalidAddress"}],"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"},{"lessThan":"1.2.1","status":"affected","version":"1.2.0","versionType":"semver"}]}],"configurations":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>Exploitation requires all of the following: an upstream whose hostPort template includes the request namespace or request metadata; a static outbound credential on that upstream; TLS verified against the system trust store with no literal tls.serverName; and a route, such as a default route, that sends the caller's namespace to that upstream. The published Temporal Cloud configuration example has this shape but listens on loopback only.</p>"}],"value":"Exploitation requires all of the following: an upstream whose hostPort template includes the request namespace or request metadata; a static outbound credential on that upstream; TLS verified against the system trust store with no literal tls.serverName; and a route, such as a default route, that sends the caller's namespace to that upstream. The published Temporal Cloud configuration example has this shape but listens on loopback only."},{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>Attack Requirements is Present because the deployment must use the upstream configuration above. Privileges Required is Low because the score assumes inbound authentication is configured; under the default, which admits every caller, no credential is needed. The subsequent-system metrics are High because the key works against the upstream Temporal service independently of the proxy.</p>"}],"value":"Attack Requirements is Present because the deployment must use the upstream configuration above. Privileges Required is Low because the score assumes inbound authentication is configured; under the default, which admits every caller, no credential is needed. The subsequent-system metrics are High because the key works against the upstream Temporal service independently of the proxy."}],"descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream's hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.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, and rotate any upstream API key that untrusted callers could reach.</p>"}],"value":"A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream's hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.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, and rotate any upstream API key that untrusted callers could reach."}],"impacts":[{"descriptions":[{"lang":"en","value":"Disclosure of the proxy's static upstream API key to a host the caller chooses. With the key, the caller can read and modify every namespace it authorizes on the upstream Temporal service, without going through the proxy, including starting, signaling, and terminating Workflows and deleting Schedules. The proxy's own data and availability are not affected."}]}],"metrics":[{"cvssV4_0":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"PRESENT","attackVector":"NETWORK","baseScore":7.3,"baseSeverity":"HIGH","exploitMaturity":"NOT_DEFINED","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"HIGH","subConfidentialityImpact":"HIGH","subIntegrityImpact":"HIGH","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"NONE","vulnerabilityResponseEffort":"NOT_DEFINED"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-918","description":"CWE-918: Server-Side Request Forgery","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-18T20:20:49.623Z","orgId":"61241ed8-fa44-4f23-92db-b8c443751968","shortName":"Temporal"},"references":[{"name":"Upstream address validation in temporal-proxy 1.2.0, which rejects only empty hosts and labels","tags":["product"],"url":"https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go#L259-L282"},{"name":"Fix pull request","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/284"},{"name":"Fix commit","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8"},{"name":"Backport pull request for the 1.0 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/294"},{"name":"Backport commit on releases/v1.0.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061"},{"name":"Backport pull request for the 1.1 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/293"},{"name":"Backport commit on releases/v1.1.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90"},{"name":"Backport pull request for the 1.2 release line","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/pull/292"},{"name":"Backport commit on releases/v1.2.x","tags":["patch"],"url":"https://github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313a"},{"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 reject a request whose templated upstream address does not render to a plain host name or IP address with an optional port, or whose templated TLS server name is not a plain host name. They also refuse at configuration load a templated hostPort or tls.serverName whose host does not end in a literal domain, as in {{ .RemoteNamespace }}.tmprl.cloud:7233, so a configuration that templates the whole host must be changed before upgrading. Rotate any upstream API key held by an affected deployment that untrusted callers could reach. 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 reject a request whose templated upstream address does not render to a plain host name or IP address with an optional port, or whose templated TLS server name is not a plain host name. They also refuse at configuration load a templated hostPort or tls.serverName whose host does not end in a literal domain, as in {{ .RemoteNamespace }}.tmprl.cloud:7233, so a configuration that templates the whole host must be changed before upgrading. Rotate any upstream API key held by an affected deployment that untrusted callers could reach. Releases before 1.0.0 receive no fix."}],"source":{"discovery":"INTERNAL"},"title":"temporal-proxy request namespace can redirect a templated upstream and leak its API key","workarounds":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>Use fixed upstream addresses, or routing rules that match literal namespace names, with no default or system route to a templated upstream. Alternatively, set a literal tls.serverName on the templated upstream, or use an external authenticator that admits only listed namespaces.</p>"}],"value":"Use fixed upstream addresses, or routing rules that match literal namespace names, with no default or system route to a templated upstream. Alternatively, set a literal tls.serverName on the templated upstream, or use an external authenticator that admits only listed namespaces."}]}},"cveMetadata":{"assignerOrgId":"61241ed8-fa44-4f23-92db-b8c443751968","assignerShortName":"Temporal","cveId":"CVE-2026-130089","datePublished":"2026-11-18T20:20:49.623Z","dateReserved":"2026-11-16T20:59:57.535Z","dateUpdated":"2026-11-18T21:19:56.314Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-18 21:17:48","lastModifiedDate":"2026-11-18 22:17:18","problem_types":["CWE-918","CWE-918 CWE-918: Server-Side Request Forgery"],"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:H/VI:N/VA:N/SC:H/SI:H/SA:H/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.3,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"PRESENT","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"NONE","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"HIGH","subIntegrityImpact":"HIGH","subAvailabilityImpact":"HIGH","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:48.680937Z","id":"CVE-2026-130089","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"130089","Ordinal":"1","Title":"temporal-proxy request namespace can redirect a templated upstre","CVE":"CVE-2026-130089","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"130089","Ordinal":"1","NoteData":"A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream's hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.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, and rotate any upstream API key that untrusted callers could reach.","Type":"Description","Title":"temporal-proxy request namespace can redirect a templated upstre"}]}}}