CVE-2026-130089 json
temporal-proxy request namespace can redirect a templated upstream and leak its API key
published 4h ago modified 2h ago also EUVD-2026-129187
- cvss
- 7.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Temporal Technologies, Inc. temporal-proxy 1.0.2, 1.1.2, 1.2.1
- github.com/temporalio/temporal-proxy@b902dcf commit
- github.com/temporalio/temporal-proxy@cd60785 commit
- github.com/temporalio/temporal-proxy@dfb4b83 commit
- github.com/temporalio/temporal-proxy@c736360 commit
- github.com/temporalio/temporal-proxy#284 pull request
- github.com/temporalio/temporal-proxy#294 pull request
- github.com/temporalio/temporal-proxy#293 pull request
- github.com/temporalio/temporal-proxy#292 pull request
- github.com/temporalio/temporal-proxy/releases/tag/v1.0.2 release
- github.com/temporalio/temporal-proxy/releases/tag/v1.1.2 release
Is CVE-2026-130089 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H |
Affected products
- Temporal Technologies, Inc. temporal-proxy
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/temporalio/temporal-proxy/pull/284
patch
-
github.com
/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8
patch
-
github.com
/temporalio/temporal-proxy/pull/294
patch
-
github.com
/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061
patch
-
github.com
/temporalio/temporal-proxy/pull/293
patch
-
github.com
/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90
patch
-
github.com
/temporalio/temporal-proxy/pull/292
patch
-
github.com
/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313a
patch
-
github.com
/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go#L259-L282
product
-
github.com
/temporalio/temporal-proxy/releases/tag/v1.0.2
release-notes
-
github.com
/temporalio/temporal-proxy/releases/tag/v1.1.2
release-notes
-
github.com
/temporalio/temporal-proxy/releases/tag/v1.2.1
release-notes
Sources
- CVE List CVE-2026-130089
- NVD CVE-2026-130089
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.