CVE-2026-130089
Received Received - Intake

Authentication Bypass in Temporal Proxy via Namespace Injection

Vulnerability report for CVE-2026-130089, 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

A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream's hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.0 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line, and rotate any upstream API key that untrusted callers could reach.

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 4 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)
Temporal Technologies, Inc. temporal-proxy From 1.2.0 (inc) to 1.2.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

A caller can send requests to the temporal-proxy gRPC listener and obtain the static API key of an upstream service by manipulating the request namespace. The proxy does not validate the namespace before using it in a templated upstream address, allowing crafted namespaces to change the proxy's target host. If the upstream verifies TLS against the system trust store without setting a literal server name, a caller-controlled host with a valid certificate can pass verification and receive the API key. This affects versions 0.1.0 through 1.2.0 of temporal-proxy.

Detection Guidance

Check if your temporal-proxy version is between 0.1.0 and 1.2.0. Run: temporal-proxy --version. Inspect gRPC listener logs for namespace-related errors or unexpected upstream connections. Monitor for unauthorized API key usage in upstream Temporal services.

Impact Analysis

An attacker could gain unauthorized access to upstream Temporal services by obtaining and using the API key. This could lead to data breaches, unauthorized workflow execution, or service disruption. Systems using templated upstream configurations are particularly at risk.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. Organizations may face compliance violations, legal penalties, and reputational damage if exploited.

Mitigation Strategies

Upgrade temporal-proxy to fixed versions (1.0.2, 1.1.2, 1.2.1 or later). Rotate any upstream API keys that untrusted callers could access. Ensure templated upstream hosts end with a literal domain (e.g., {{ .RemoteNamespace }}.tmprl.cloud:7233).

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130089. 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...