CVE-2026-130089: high-severity vulnerability in temporal-proxy
temporal-proxy request namespace can redirect a templated upstream and leak its API key
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.3epss 0.3%
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.
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
Affected products
Temporal Technologies, Inc. · temporal-proxyRelated CVEs — temporal-proxy
In the same product, most dangerous first.
CVE-2026-130092HIGHUnauthenticated callers can exhaust temporal-proxy memory through unbounded request metricsEPSS 0.6%CVE-2026-132559LOWtemporal-proxy can send decrypted failure messages and stack traces to the upstream in plaintextEPSS 0.5%CVE-2026-130091HIGHtemporal-proxy can be terminated by memory exhaustion when decompressing stored payloadsEPSS 0.5%CVE-2026-130090LOWtemporal-proxy can send a request under another upstream's credential when templated upstreams render the same addressEPSS 0.5%CVE-2026-108126MEDIUMtemporal-proxy payload decryption is not bound to the request namespaceEPSS 0.4%
References
https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go#L259-L282https://github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8https://github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313ahttps://github.com/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061https://github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90https://github.com/temporalio/temporal-proxy/pull/284https://github.com/temporalio/temporal-proxy/pull/292https://github.com/temporalio/temporal-proxy/pull/293https://github.com/temporalio/temporal-proxy/pull/294https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1