CVE-2026-130090: low-severity vulnerability in temporal-proxy
temporal-proxy can send a request under another upstream's credential when templated upstreams render the same address
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
8Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 2.3epss 0.5%
When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream's credential, namespace translation, and payload encryption keys. temporal-proxy pools connections for templated upstreams by rendered address and TLS server name only, although each upstream's outbound credential, namespace translation, and payload encryption keys, where configured, are attached to its connection. A request routed to one upstream can therefore be sent over the connection the other created, and the upstream Temporal service authorizes it as the other upstream's principal. Configuration validation rejects only identical hostPort values, so templates that differ in text but render the same address are accepted. This mixes the two upstreams' ordinary traffic, and a caller that an external authenticator restricts to one upstream's namespaces can use it to act under the other upstream's credential. Deployments with at most one templated upstream are not affected. temporal-proxy versions 0.1.0 through 1.1.1 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.0, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
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-108126MEDIUMtemporal-proxy payload decryption is not bound to the request namespaceEPSS 0.4%CVE-2026-130089HIGHtemporal-proxy request namespace can redirect a templated upstream and leak its API keyEPSS 0.3%
References
https://github.com/temporalio/temporal-proxy/commit/9d1dc1dcf92fef191e61e9076ff46fd7c8570702https://github.com/temporalio/temporal-proxy/commit/d201e99150e90e34b033480f91022067f39b3c8ehttps://github.com/temporalio/temporal-proxy/commit/d7228fac60798e4047e00606b8b41573ab2f77c4https://github.com/temporalio/temporal-proxy/pull/279https://github.com/temporalio/temporal-proxy/pull/285https://github.com/temporalio/temporal-proxy/pull/286https://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.0