CVE-2026-130090
Received Received - Intake

Authentication Bypass in Temporal Proxy via Templated Upstreams

Vulnerability report for CVE-2026-130090, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: Temporal Technologies Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
Temporal Technologies, Inc. temporal-proxy From 0.1.0 (inc) to 0.10.1 (inc)
Temporal Technologies, Inc. temporal-proxy From 1.0.0 (inc) to 1.0.2 (exc)
Temporal Technologies, Inc. temporal-proxy From 1.1.0 (inc) to 1.1.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-488 The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in temporal-proxy occurs when two templated upstreams render the same address but use different credentials or configurations. The proxy incorrectly shares pooled connections between these upstreams, causing requests routed to one upstream to be sent using the other upstream's credentials, namespace translation, or payload encryption keys. This allows unauthorized access under the other upstream's identity.

Detection Guidance

Detecting this vulnerability requires checking if temporal-proxy versions 0.1.0 through 1.1.1 are deployed. Use commands like 'temporal-proxy --version' or inspect Docker images for the vulnerable version. If using Kubernetes, check pod images with 'kubectl get pods -o jsonpath='{.spec.containers[0].image}''. Upgrade to fixed versions (1.0.2, 1.1.2, or 1.2.0) immediately.

Impact Analysis

This vulnerability can lead to credential leakage, namespace misconfiguration, and unauthorized access. Attackers could exploit it to perform actions under a different upstream's identity, bypassing access controls. Deployments with multiple templated upstreams are most at risk.

Compliance Impact

This vulnerability could violate compliance requirements by enabling unauthorized access to sensitive data or systems. It may lead to data breaches, improper access controls, and failure to maintain data integrity, which are critical violations under GDPR and HIPAA.

Mitigation Strategies

Upgrade temporal-proxy to version 1.0.2, 1.1.2, 1.2.0, or later depending on your minor release line. Deployments with only one templated upstream are not affected.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130090. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...