CVE-2026-130090 temporal-proxy can send a request under another upstream's credential when templated upstreams render the same address

Low 2.3 Published Updated

Callers restricted to one upstream's namespaces can act under another upstream's credentials when templated upstreams render the same address; Temporal deployments 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-130090?

CVE-2026-130090 is a low-severity authentication bypass 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

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.

Weakness: CWE-488

Which versions are affected by CVE-2026-130090?

Only installations with a non-default setting turned on are exposed.

How do I fix CVE-2026-130090?

No fix has been published for CVE-2026-130090 yet. Limit exposure of the affected software until one is available.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-130090 being exploited?

There is no known exploitation of CVE-2026-130090 in the wild and no public exploit code.

Sources

Also known as GHSA-89m7-vv2p-xp63.

Is CVE-2026-130090 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free