llamaCVEVulnerability Intelligence
/
Temporal Technologies temporal-proxy

CVE-2026-130092

Temporal Technologies temporal-proxy denial of service in gRPC metrics

Anyone who can reach the gRPC port, even unauthenticated, can crash the process by sending many distinct method names.

Texto original en inglés · Ver en español

Afecta la configuración por defectoSin parche publicadodenial of service
Descargar PNG JSON
CVSS 4.0
8.7
Alta
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N Fuente: CNA
ExplotaciónSin evidenciaSSVC: ninguna · no figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición3 dDesde la divulgación, 18 nov 2026, 3:18 p. m.
Detección10 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, automatizable e impacto técnico parcial. No hay versión corregida: aplique mitigaciones.
Agéndala y deja de pensar en ella.Sospechosa como un adjunto llamado factura_final2.exe.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +2
Explotación
Remediación
Monitoreo
Detectada +3
18 nov 26
21 nov 26
18 nov 26
19 nov 26
20 nov 26
21 nov 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-130092 divulgada · CVSS 8.7 (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
Resumen
Resumen generado por IA · CC-BY 4.0 · 18 nov 2026

Temporal-proxy, a product from Temporal Technologies, Inc., can be driven to exhaust its memory and crash. A caller who can reach its gRPC listener, with or without valid credentials, can send requests with many distinct gRPC method names, and the proxy keeps a metric series for each one, so memory grows until the process is terminated.

Affects temporal-proxy 0.1.0-alpha.20260716 through 0.10.1 and 1.0.0 through 1.2.0 before their fixes, where callers can reach the gRPC listener. Fixed in 1.0.2, 1.1.2, and 1.2.1.

¿Qué significa?Unauthenticated callers can make temporal-proxy keep adding request metrics without any limit, so its memory use can grow until it is exhausted.
¿Quién está afectado?The affected ranges are 0.1.0-alpha.20260716 through 0.10.1, and 1.0.0 before 1.0.2, 1.1.0 before 1.1.2, and 1.2.0 before 1.2.1. The advisory says every deployment whose gRPC listener the caller can reach is affected, so compare the deployed temporal-proxy version with these ranges and check who can reach the gRPC listener.
¿Qué hacer?Upgrade to temporal-proxy 1.0.2, 1.1.2, or 1.2.1, as appropriate for the deployed minor release line.
Descripción original del registro (Temporal)

A caller who can reach the temporal-proxy gRPC listener, with or without a valid credential, can grow the proxy's memory until the process is terminated by sending requests with many distinct gRPC method names. temporal-proxy labels its request metrics with the method name exactly as the caller sent it, and records every request, including those that authentication or routing reject. Each distinct method name adds metric series that are never removed. The series grow whether or not the metrics endpoint is scraped, and metric labels configured from request metadata multiply the growth. temporal-proxy versions 0.1.0-alpha.20260716 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.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
The caller can reach the proxy's gRPC listener“Every deployment whose gRPC listener the caller can reach is affected.”
MitigaciónRestrict network access to the proxy's gRPC listener to trusted clients, or place the proxy behind a gateway that forwards only known Temporal service method paths.
Vector CVSS 4.0

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
Requisitos de ataqueAT:N
NingunoPresentes
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaPasivaActiva
Confid. (sistema)VC:N
AltoBajoNinguno
Integridad (sistema)VI:N
AltoBajoNinguno
Disponib. (sistema)VA:H
AltoBajoNinguno
Confid. (posterior)SC:N
AltoBajoNinguno
Integridad (posterior)SI:N
AltoBajoNinguno
Disponib. (posterior)SA:N
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
10.0/ 10Muy alto
Vector 10.0 (muy fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida Última
github.com/temporalio/temporal-proxy≥ 0.1.0-alpha.20260716 ≤ 0.10.1
github.com/temporalio/temporal-proxy≥ 1.0.0 < 1.0.2
github.com/temporalio/temporal-proxy≥ 1.1.0 < 1.1.2
github.com/temporalio/temporal-proxy≥ 1.2.0 < 1.2.1
0.1.0-alpha.20260716
v0.9.1
0.10.1
1.0.0
1.0.2
1.1.0
1.1.2
1.2.0
1.2.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogithub.com/temporalio/temporal-proxy
Sin parche — — v0.9.1 afectada
Versiones corregidas1.0.21.1.21.2.1
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Registro
EscenarioGENERALTemporal
configurationEvery deployment whose gRPC listener the caller can reach is affected. No setting is required, and inbound authentication does not mitigate the issue, because requests that authentication rejects are still recorded.Temporal
configurationThe Vulnerable System Availability metric is High because the loss of service is total and lasts for as long as the caller keeps sending requests.Temporal
MitigaciónRestrict network access to the proxy's gRPC listener to trusted clients, or place the proxy behind a gateway that forwards only known Temporal service method paths.Temporal
solutionUpgrade to temporal-proxy 1.0.2, 1.1.2, or 1.2.1, as appropriate for the deployed minor release line. Fixed releases report any method outside the services the proxy forwards as unknown and limit each metadata label to 100 distinct values. Releases before 1.0.0 receive no fix.Temporal
Referencias
Parchehttps://github.com/temporalio/temporal-proxy/pull/288
Parchehttps://github.com/temporalio/temporal-proxy/commit/f745e71918dc386524a606eff1153dbd0f2b0091
Parchehttps://github.com/temporalio/temporal-proxy/pull/289
Parchehttps://github.com/temporalio/temporal-proxy/commit/87254989bf135dfaf8176e0c822d24aa86907c78
Parchehttps://github.com/temporalio/temporal-proxy/pull/290
Parchehttps://github.com/temporalio/temporal-proxy/commit/700fc2eae5196ce612eac4b7e8e25877269f6c05
Parchehttps://github.com/temporalio/temporal-proxy/pull/291
Parchehttps://github.com/temporalio/temporal-proxy/commit/4b9aba1b14d9b656c32bb3394de7ab820b33c98a
Otrahttps://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/server/reporter.go#L69-L94
Otrahttps://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/dataplane/dataplane.go#L185-L192
Otrahttps://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2
Otrahttps://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2
Ver 1 referencias más
Otrahttps://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.