CVE-2026-130089 temporal-proxy request namespace can redirect a templated upstream and leak its API key
Callers can redirect templated upstream addresses to a trusted host and steal its API key; Temporal proxy operators should care.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Harmful if only installed
- No
- Needs a specific call
- No
- Fix
- None listed
What is CVE-2026-130089?
CVE-2026-130089 is a high-severity server-side request forgery vulnerability in temporal-proxy, published on 18 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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
Which versions are affected by CVE-2026-130089?
An affected version is exposed as installed. No special setting or call is needed.
How do I fix CVE-2026-130089?
No fix has been published for CVE-2026-130089 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-130089 being exploited?
There is no known exploitation of CVE-2026-130089 in the wild and no public exploit code.
Sources
Also known as GHSA-2jp8-mqrx-3pcm.