When Two Templated Upstreams
Source GCVE Database
Not known to be exploited · CVSS 2.3 Low : upgrade to 1.1.2 or 1.0.2 when convenient.
Data as of 18 Nov 2026, 22:51 UTC
Thin evidence
One scorer or none| CNA (Temporal) | CVSS 4.0 | 2.3 |
|---|
- Patch
- Available – fixed in 1.1.2, 1.0.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade temporal-proxy and github.com/temporalio/temporal-proxy to 1.1.2 or 1.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| temporal-proxygithub.com/temporalio/temporal-proxy | Affected
| Fixed in
|
Gogithub.com/temporalio/temporal-proxypkg:golang/github.com/temporalio/temporal-proxyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade temporal-proxy to version 1.0.2, 1.1.2, or 1.2.0 depending on the deployed minor release line. Deployments with only one templated upstream are not affected. No other mitigations are indicated.
Description
A vulnerability in temporal-proxy versions 0.1.0 through 1.1.1 allows requests routed to one templated upstream to be sent using another upstream's credentials and encryption keys if both render the same address. This occurs because temporal-proxy pools connections by rendered address and TLS server name only, mixing traffic between upstreams with different credentials. Deployments with only one templated upstream are not affected. The issue is fixed in versions 1.0.2, 1.1.2, and 1.2.0.
References
- nvd.nist.gov/vuln/detail/CVE-2026-130090 (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/279 (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/285 (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/286 (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/9d1dc1dcf92fef191e61e9076ff46fd7c8570702 (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/d201e99150e90e34b033480f91022067f39b3c8e (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/d7228fac60798e4047e00606b8b41573ab2f77c4 (opens in a new tab)
- github.com/temporalio/temporal-proxy/releases/tag/v1.0.2 (opens in a new tab)
- github.com/temporalio/temporal-proxy/releases/tag/v1.1.2 (opens in a new tab)
- github.com/temporalio/temporal-proxy/releases/tag/v1.2.0 (opens in a new tab)