CVE
Temporal Technologies temporal-proxy SSRF leaks upstream API key via namespace routing
Affects temporal-proxy 0.1.0 to 0.10.1 and earlier 1.x releases before each fix when an upstream hostPort is templated from the request namespace or metadata with a static credential. Fixed in 1.0.2, 1.1.2, and 1.2.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.0.2, 1.1.2, 1.2.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Upstream hostPort is templated from the request namespace or request metadata Upstream uses a static outbound credential TLS is verified against the system trust store with no literal tls.serverName set A route, such as a default route, sends the caller's namespace to the templated upstream
Summary
temporal-proxy from Temporal Technologies lets a remote caller with low-privilege login to its gRPC listener obtain the static API key of an upstream whose address is built from the request namespace. The attacker can then use that key directly against the upstream Temporal service.
Original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity7.3/10CVSS 7.3
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 32 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Upstream hostPort is templated from the request namespace or request metadata Upstream uses a static outbound credential TLS is verified against the system trust store with no literal tls.serverName set A route, such as a default route, sends the caller's namespace to the templated upstreamUpgrade to a fixed version: 1.0.2, 1.1.2, 1.2.1.
Workaround: Use fixed upstream addresses, or routing rules that match literal namespace names, with no default or system route to a templated upstream. Alternatively, set a literal tls.serverName on the templated upstream, or use an external authenticator that admits only listed namespaces.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130089 (temporal-proxy request namespace can redirect a templated upstream and leak its API key), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130089 (entry last updated 2026-11-18):
Affected:
- Go package github.com/temporalio/temporal-proxy: from 0.1.0, through 0.10.1; from 1.0.0, fixed in 1.0.2; from 1.1.0, fixed in 1.1.2; from 1.2.0, fixed in 1.2.1
Fixed versions: 1.0.2, 1.1.2, 1.2.1.
Conditions (all must be true for the bug to be hit):
- Upstream hostPort is templated from the request namespace or request metadata (source: https://www.cve.org/CVERecord?id=CVE-2026-130089)
- Upstream uses a static outbound credential (source: https://www.cve.org/CVERecord?id=CVE-2026-130089)
- TLS is verified against the system trust store with no literal tls.serverName set (source: https://www.cve.org/CVERecord?id=CVE-2026-130089)
- A route, such as a default route, sends the caller's namespace to the templated upstream (source: https://www.cve.org/CVERecord?id=CVE-2026-130089)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Use fixed upstream addresses, or routing rules that match literal namespace names, with no default or system route to a templated upstream. Alternatively, set a literal tls.serverName on the templated upstream, or use an external authenticator that admits only listed namespaces. (source: https://www.cve.org/CVERecord?id=CVE-2026-130089)
CISA KEV: CVE-2026-130089 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130089 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/temporalio/temporal-proxy/pull/284
- https://github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8
- https://github.com/temporalio/temporal-proxy/pull/294
- https://github.com/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061
- https://github.com/temporalio/temporal-proxy/pull/293
- https://github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90
- https://github.com/temporalio/temporal-proxy/pull/292
- https://github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313a
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130089
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130089"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
From 0.1.0 · through 0.10.1; From 1.0.0 · fixed in 1.0.2; From 1.1.0 · fixed in 1.1.2; From 1.2.0 · fixed in 1.2.1
Evidence 14
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130089
Is CVE-2026-130089 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A caller's request namespace or request metadata can redirect a templated upstream to a different host, which leaks that upstream's static API key.Source: cve.org
Which versions are affected by CVE-2026-130089?
github.com/temporalio/temporal-proxy (Go): from 0.1.0 through 0.10.1; from 1.0.0 before 1.0.2; from 1.1.0 before 1.1.2; from 1.2.0 before 1.2.1.Source: cve.now feed data
Am I affected, and how do I check?
Affected are temporal-proxy 0.1.0 through 0.10.1, 1.0.0 before 1.0.2, 1.1.0 before 1.1.2, and 1.2.0 before 1.2.1. The setup also needs a templated upstream hostPort, a static outbound credential on that upstream, TLS verified against the system trust store with no literal tls.serverName, and a route such as a default route that sends the caller's namespace to that upstream. Check the installed version and the upstream and route configuration.Source: cve.org
How do I fix CVE-2026-130089?
Upgrade to temporal-proxy 1.0.2, 1.1.2, or 1.2.1, matching the deployed minor release line. Until the upgrade is applied, use fixed upstream addresses or routing rules that match literal namespace names, with no default or system route to a templated upstream, or set a literal tls.serverName on the templated upstream.Source: cve.org