Skip to content
Threat Brief

← All advisories

CVE-2026-130089

High 7.3No known exploitationFix available

temporal-proxy request namespace can redirect a templated upstream and leak its API key

Record last updated

CVSS score

7.3

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 29% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-918

Patching and mitigation

Patch status
Fix available (source: CVE record (Temporal))
Fix documented (source date)
Vendor solution
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.
Mitigation
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.
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Temporal Technologies, Inc.temporal-proxyfrom 0.1.0 up to and including 0.10.1Not documentedCVE Program
Temporal Technologies, Inc.temporal-proxyfrom 1.0.0 before 1.0.21.0.2CVE Program
Temporal Technologies, Inc.temporal-proxyfrom 1.1.0 before 1.1.21.1.2CVE Program
Temporal Technologies, Inc.temporal-proxyfrom 1.2.0 before 1.2.11.2.1CVE Program

Timeline

  1. Disclosure

    CVE record published by Temporal

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Temporal)

    Source: CVE record (Temporal) (opens in a new tab)

Vendor guidance and references