CVE-2026-130090
Temporal Technologies temporal-proxy authorization bypass in upstream connection pool
A low-privileged network caller can have requests authorized as another upstream's principal.
Texto original en inglés · Ver en español
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-130090 divulgada · CVSS 2.3 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
temporal-proxy from Temporal Technologies, Inc. can send a request under another upstream's credential when two templated upstreams render the same address, because it pools connections by rendered address and TLS server name only. A network caller with low privileges can use this to have the Temporal service authorize requests as the other upstream's principal, and where an external authenticator limits the caller to one upstream's namespaces, to act under the other upstream's credential.
Descripción original del registro (Temporal)
When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream's credential, namespace translation, and payload encryption keys. temporal-proxy pools connections for templated upstreams by rendered address and TLS server name only, although each upstream's outbound credential, namespace translation, and payload encryption keys, where configured, are attached to its connection. A request routed to one upstream can therefore be sent over the connection the other created, and the upstream Temporal service authorizes it as the other upstream's principal. Configuration validation rejects only identical hostPort values, so templates that differ in text but render the same address are accepted. This mixes the two upstreams' ordinary traffic, and a caller that an external authenticator restricts to one upstream's namespaces can use it to act under the other upstream's credential. Deployments with at most one templated upstream are not affected. temporal-proxy versions 0.1.0 through 1.1.1 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.0, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line.
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.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/temporalio/temporal-proxy/pull/279https://github.com/temporalio/temporal-proxy/commit/d7228fac60798e4047e00606b8b41573ab2f77c4https://github.com/temporalio/temporal-proxy/pull/286https://github.com/temporalio/temporal-proxy/commit/9d1dc1dcf92fef191e61e9076ff46fd7c8570702https://github.com/temporalio/temporal-proxy/pull/285https://github.com/temporalio/temporal-proxy/commit/d201e99150e90e34b033480f91022067f39b3c8ehttps://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.0Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
