CVE-2026-130089temporal-proxy request namespace can redirect a templated upstream and leak its API key
- 7.3HighCVSS base score
- —Exploitation in 30 daysno EPSS score yet
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Temporal
- 2 days later
· 2 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| TemporalCNA (assigner) | 4.0 | High7.3 | 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 |
| NVDNVD · Received | 4.0 | High7.3 | 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 |
- EPSS (exploitation in 30 days)
- Not scored
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.
Affected products
Temporal Technologies, Inc. · temporal-proxy
- affected 0.1.0 – ≤ 0.10.1
- affected 1.0.0 – < 1.0.2
- affected 1.1.0 – < 1.1.2
- affected 1.2.0 – < 1.2.1
What to do
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.
Workaround: 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.
References
References12
- Upstream address validation in temporal-proxy 1.2.0, which rejects only empty hosts and labels (opens in a new tab)product
- Fix pull request (opens in a new tab)patch
- Fix commit (opens in a new tab)patch
- Backport pull request for the 1.0 release line (opens in a new tab)patch
- Backport commit on releases/v1.0.x (opens in a new tab)patch
- Backport pull request for the 1.1 release line (opens in a new tab)patch
- Backport commit on releases/v1.1.x (opens in a new tab)patch
- Backport pull request for the 1.2 release line (opens in a new tab)patch
- Backport commit on releases/v1.2.x (opens in a new tab)patch
- temporal-proxy 1.0.2 (opens in a new tab)release-notes
- temporal-proxy 1.1.2 (opens in a new tab)release-notes
- temporal-proxy 1.2.1 (opens in a new tab)release-notes
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-130089)Record last updated .