llamaCVEVulnerability Intelligence
/
Temporal Technologies temporal-proxy

CVE-2026-132559

Temporal Technologies temporal-proxy plaintext exposure of failure data in workflow history

A low-privilege attacker can expose decrypted failure messages and stack traces to anyone reading workflow history.

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

Sin parche publicadosecurity flaw
Descargar PNG JSON
CVSS 4.0
2.3
Baja
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/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:30 p. m.
Detección15 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, no automatizable e impacto técnico parcial. No hay versión corregida: aplique mitigaciones.
Ni el pentester más aburrido usaría esto.Bajo impacto. Igual parchea cuando toque, ¿eh?
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Modificada
Explotación
Remediación
Monitoreo
Detectada +2
Verificada
18 nov 26
19 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-132559 divulgada · CVSS 2.3 (CNA)
Monitoreo Detectada Ingresó al índice
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
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 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 Technologies' temporal-proxy can store decrypted failure messages and stack traces in plaintext at the upstream Temporal service, where anyone who can read the Workflow's history can see them. A remote attacker with low-privilege access can trigger this by sending a failure back through the proxy, which forwards the restored text unchanged.

Descripción original del registro (Temporal)

When payload encryption is enabled, failure messages and stack traces that temporal-proxy is configured to keep from the upstream Temporal service can reach it in plaintext, where anyone who can read the Workflow's history at the upstream can read them. When the proxy returns a failure to a Worker, it decrypts the failure's encoded attributes and copies the message and stack trace back onto the failure, keeping the attributes. A Worker that sends that failure back through the proxy, as SDKs do when an Activity failure becomes the cause of a Workflow failure, sends the restored text with it, and the proxy forwards the text unchanged because the failure already has encoded attributes. The upstream then stores the text in plaintext beside its encrypted copy. This affects deployments that enable failure encryption in the proxy, and deployments that leave it off while the SDK encodes failure attributes itself. Payloads are not affected. temporal-proxy versions 0.9.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.

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:P
NingunoPresentes
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaPasivaActiva
Confid. (sistema)VC:L
AltoBajoNinguno
Integridad (sistema)VI:N
AltoBajoNinguno
Disponib. (sistema)VA:N
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
5.9/ 10Medio
Vector 5.9 (moderada) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida Última
github.com/temporalio/temporal-proxy≥ 0.9.0 ≤ 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.9.0
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
configurationExposure requires all of the following. Payload encryption is enabled; it is off by default. Failure text is moved into encoded attributes, either by the proxy (encryption.failures) or by the SDK, for example the Go SDK's EncodeCommonAttributes option. A Worker sends back a failure it received through the proxy. The reader can read Workflow history at the upstream Temporal service without going through the proxy, for example a user with read access to the namespace, the upstream's operator, or anyone with access to its storage.Temporal
configurationThe Attack Requirements metric is Present because the exposure depends on the encryption configuration and on Worker code sending back a received failure, neither of which the reader controls. Confidentiality is Low because only failure messages and stack traces are exposed, the reader does not choose which, and payloads stay encrypted.Temporal
MitigaciónNo proxy setting closes this issue: with encryption.failures off, the proxy still restores failure text that the SDK encoded, and a Worker that sends it back still sends it in plaintext. Until a fixed release is deployed, keep sensitive data out of failure messages and stack traces.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 replace the message and clear the stack trace of every outbound failure that carries encoded attributes, in any encoding, whenever the proxy is configured with encryption keys, whether or not encryption.failures is set. A custom failure converter that sends readable text beside its own encoded attributes will find that text replaced at the upstream. Upgrading does not re-encrypt failure text the upstream already stores. Releases before 1.0.0 receive no fix.Temporal
Referencias
Parchehttps://github.com/temporalio/temporal-proxy/pull/296
Parchehttps://github.com/temporalio/temporal-proxy/commit/68dea481cdd8112432d5efb495b0963e03fff14d
Parchehttps://github.com/temporalio/temporal-proxy/pull/305
Parchehttps://github.com/temporalio/temporal-proxy/commit/53710919feb8af12e2f4b789e2d997a412cdd33f
Parchehttps://github.com/temporalio/temporal-proxy/pull/304
Parchehttps://github.com/temporalio/temporal-proxy/commit/95b99dceaa1a19c666b1661e2edef4090acda119
Parchehttps://github.com/temporalio/temporal-proxy/pull/308
Parchehttps://github.com/temporalio/temporal-proxy/commit/85492b5728362d8fd082e5cff9290a23c016ae30
Parchehttps://github.com/temporalio/temporal-proxy/pull/303
Parchehttps://github.com/temporalio/temporal-proxy/commit/8bd1045ccfaaa54580444dd9855fd87f3b1b252b
Parchehttps://github.com/temporalio/temporal-proxy/pull/307
Parchehttps://github.com/temporalio/temporal-proxy/commit/7742a645c526dde4b6a182e6e55e2f9d9ea2b43b
Ver 9 referencias más
Parchehttps://github.com/temporalio/temporal-proxy/pull/302
Parchehttps://github.com/temporalio/temporal-proxy/commit/c5d211cda68a7c07ec691b3b47f1c0ab6fc495fb
Parchehttps://github.com/temporalio/temporal-proxy/pull/306
Parchehttps://github.com/temporalio/temporal-proxy/commit/ea541ae21fbfda65bd867a88020ddfce0b92c907
Otrahttps://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L26-L29
Otrahttps://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/failure.go#L55-L70
Otrahttps://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2
Otrahttps://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2
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.