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
Source GCVE Database
Not known to be exploited · CVSS 7.3 High · fixed in 1.2.1 : patch temporal-proxy soon.
Data as of 18 Nov 2026, 22:34 UTC
Thin evidence
One scorer or none| CNA (Temporal) | CVSS 4.0 | 7.3 |
|---|
- Patch
- Available – fixed in 1.2.1, 1.1.2, 1.0.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade temporal-proxy and github.com/temporalio/temporal-proxy to 1.2.1, 1.1.2 or 1.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| temporal-proxygithub.com/temporalio/temporal-proxy | Affected
| Fixed in
|
Gogithub.com/temporalio/temporal-proxypkg:golang/github.com/temporalio/temporal-proxyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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. Upgrade to the fixed release for the deployed minor release line, and rotate any upstream API key that untrusted callers could reach.
References
- nvd.nist.gov/vuln/detail/CVE-2026-130089 (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/284 (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/292 (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/293 (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/294 (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8 (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313a (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061 (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90 (opens in a new tab)
- github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go (opens in a new tab)
- github.com/temporalio/temporal-proxy/releases/tag/v1.0.2 (opens in a new tab)
- github.com/temporalio/temporal-proxy/releases/tag/v1.1.2 (opens in a new tab)
- github.com/temporalio/temporal-proxy/releases/tag/v1.2.1 (opens in a new tab)