CVE-2026-130090
Description
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.
Is your site exposed to CVE-2026-130090?
Run a free security scan — no signup, results in seconds.
Weakness Type (CWE)
References
Other References
Frequently Asked Questions
What is CVE-2026-130090? +
How do I check if I'm vulnerable to CVE-2026-130090? +
Related Vulnerabilities
Exposure of Data Element to Wrong Session vulnerability in ash-project ash_graphql can deliver one subscription's resolved records to a different …
An Incorrect Implementation of Authentication Algorithm and Exposure of Data Element to Wrong Ses-sion vulnerability in the session handling used …
Exposure of data element to wrong session vulnerability in Apache APISIX. This issue affects Apache APISIX: from 2.3.0 before 3.7.0. …
Robots::Validate versions from 0.4.3 before 0.4.10 for Perl report clients as imposter robots when User-Agent matcher state carries over from …
Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the …
The terraform-mcp-server before version 1.1.0 is vulnerable to a cross-tenant credential reuse issue in the streamable-HTTP stateless transport mode that …