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

> 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.

- **Severity:** Low 2.3 (`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`)
- **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 available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-89m7-vv2p-xp63

## 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 (Exposure of Data Element to Wrong Session)

## 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.

## Is CVE-2026-130090 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130090 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-130090 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected product: temporal-proxy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130090/ (Markdown: https://insights.sbomify.com/CVE-2026-130090/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130090
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130090
- OSV: https://osv.dev/vulnerability/CVE-2026-130090

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130090/
Summaries are generated and may contain mistakes; the official description above is the record.
