Skip to main content
VulnerabilityPublished

CVE-2026-130090: temporal-proxy · Exposure of Data Element to Wrong Session

Affects temporal-proxySource CVE Database V5

0
Compare

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, 20:49 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.

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. Upgrade to the fixed release for the deployed minor release line.

References

Community reviews

Loading reviews…