CVE-2026-130089
Temporal Technologies temporal-proxy SSRF leaks upstream API key via namespace routing
A remote attacker with low-privilege access can steal an upstream's static API key and use it directly.
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
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-130089 divulgada · CVSS 7.3 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
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.
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.
Descripción original del registro (Temporal)
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.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/temporalio/temporal-proxy |
Sin parche | — | — | v0.9.1 afectada |
1.0.21.1.21.2.1Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/temporalio/temporal-proxy/pull/284https://github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8https://github.com/temporalio/temporal-proxy/pull/294https://github.com/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061https://github.com/temporalio/temporal-proxy/pull/293https://github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90https://github.com/temporalio/temporal-proxy/pull/292https://github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313ahttps://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go#L259-L282https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
