CVE-2026-130090
Low 2.3No known exploitationFix availabletemporal-proxy can send a request under another upstream's credential when templated upstreams render the same address
Record last updated
CVSS score
Low on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 40% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Temporal))
- Fix documented (source date)
- Vendor solution
- Upgrade to temporal-proxy 1.2.0 or later, or to 1.0.2 or 1.1.2 on those release lines. Fixed releases scope each pooled connection to the upstream that created it. Releases before 1.0.0 receive no fix.
- Mitigation
- Configure templated upstreams so that no two can render the same address, for example by giving each hostPort template a distinct fixed suffix.
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Temporal Technologies, Inc. | temporal-proxy | from 0.1.0 up to and including 0.10.1 | Not documented | CVE Program |
| Temporal Technologies, Inc. | temporal-proxy | from 1.0.0 before 1.0.2 | 1.0.2 | CVE Program |
| Temporal Technologies, Inc. | temporal-proxy | from 1.1.0 before 1.1.2 | 1.1.2 | CVE Program |
Timeline
Disclosure
CVE record published by Temporal
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Temporal)
Vendor guidance and references
- Backport commit on releases/v1.0.x (opens in a new tab)patch
- Backport commit on releases/v1.1.x (opens in a new tab)patch
- Fix commit (opens in a new tab)patch
- Fix pull request (opens in a new tab)patch
- Backport pull request for the 1.1 release line (opens in a new tab)patch
- Backport pull request for the 1.0 release line (opens in a new tab)patch
- temporal-proxy 1.0.2 (opens in a new tab)release-notes
- temporal-proxy 1.1.2 (opens in a new tab)release-notes
- temporal-proxy 1.2.0 (opens in a new tab)release-notes