CVE-2026-130090 json
temporal-proxy can send a request under another upstream's credential when templated upstreams render the same address
published 4h ago modified 2h ago also EUVD-2026-129193
- cvss
- 2.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Temporal Technologies, Inc. temporal-proxy 1.0.2, 1.1.2
- github.com/temporalio/temporal-proxy@d7228fa commit
- github.com/temporalio/temporal-proxy@9d1dc1d commit
- github.com/temporalio/temporal-proxy@d201e99 commit
- github.com/temporalio/temporal-proxy#279 pull request
- github.com/temporalio/temporal-proxy#286 pull request
- github.com/temporalio/temporal-proxy#285 pull request
- github.com/temporalio/temporal-proxy/releases/tag/v1.0.2 release
- github.com/temporalio/temporal-proxy/releases/tag/v1.1.2 release
- github.com/temporalio/temporal-proxy/releases/tag/v1.2.0 release
Is CVE-2026-130090 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
Affected products
- Temporal Technologies, Inc. temporal-proxy
Classification
- Weakness
-
- CWE-488 Exposure of Data Element to Wrong Session
References
-
github.com
/temporalio/temporal-proxy/pull/279
patch
-
github.com
/temporalio/temporal-proxy/commit/d7228fac60798e4047e00606b8b41573ab2f77c4
patch
-
github.com
/temporalio/temporal-proxy/pull/286
patch
-
github.com
/temporalio/temporal-proxy/commit/9d1dc1dcf92fef191e61e9076ff46fd7c8570702
patch
-
github.com
/temporalio/temporal-proxy/pull/285
patch
-
github.com
/temporalio/temporal-proxy/commit/d201e99150e90e34b033480f91022067f39b3c8e
patch
-
github.com
/temporalio/temporal-proxy/releases/tag/v1.0.2
release-notes
-
github.com
/temporalio/temporal-proxy/releases/tag/v1.1.2
release-notes
-
github.com
/temporalio/temporal-proxy/releases/tag/v1.2.0
release-notes
Sources
- CVE List CVE-2026-130090
- NVD CVE-2026-130090
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.