7.3
HIGH CVSS 4.0
CVE-2026-130089
temporal-proxy request namespace can redirect a templated upstream and leak its API key
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.

INFO

Published Date :

Nov. 18, 2026, 9:17 p.m.

Last Modified :

Nov. 18, 2026, 10:17 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-130089 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 134c704f-9b21-4f2e-91b3-4a467353bcc0
CVSS 4.0 HIGH 61241ed8-fa44-4f23-92db-b8c443751968
CVSS 4.0 HIGH [email protected]
Solution
Upgrade temporal-proxy to a patched version and rotate compromised API keys.
  • Upgrade temporal-proxy to a fixed release.
  • Rotate any upstream API keys that were exposed.
  • Configure external authenticator to restrict namespaces.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-130089 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-130089 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-130089 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-130089 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Nov. 18, 2026

    Action Type Old Value New Value
    Added SSVC {'id': 'CVE-2026-130089', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-11-18T21:19:48.680937Z'}
  • New CVE Received by [email protected]

    Nov. 18, 2026

    Action Type Old Value New Value
    Added 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.
    Added CVSS V4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
    Added CWE CWE-918
    Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/130xxx/CVE-2026-130089.json">CVE-2026-130089</a>
    Added Reference https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go#L259-L282
    Added Reference https://github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8
    Added Reference https://github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313a
    Added Reference https://github.com/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061
    Added Reference https://github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90
    Added Reference https://github.com/temporalio/temporal-proxy/pull/284
    Added Reference https://github.com/temporalio/temporal-proxy/pull/292
    Added Reference https://github.com/temporalio/temporal-proxy/pull/293
    Added Reference https://github.com/temporalio/temporal-proxy/pull/294
    Added Reference https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2
    Added Reference https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2
    Added Reference https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.