Skip to main content
CVE-2026-130090VulnerabilityPublished

When Two Templated Upstreams

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130090· Low 2.3

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

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Temporal)CVSS 4.02.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
temporal-proxygithub.com/temporalio/temporal-proxyAffected
  • >=0.1.0 <=0.10.1
  • >=1.0.0 <1.0.2
  • >=1.1.0 <1.1.2
Fixed in
  • 1.1.2
  • 1.0.2
Gogithub.com/temporalio/temporal-proxypkg:golang/github.com/temporalio/temporal-proxyOther threatsAffected
  • >=0.1.0 <=0.10.1
  • >=1.0.0 <1.0.2
  • >=1.1.0 <1.1.2
Fixed in
  • 1.0.2
  • 1.1.2

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

Community reviews

Loading reviews…