Cross Namespace Access via Batch Operation

Summary

A writer role user in an attacker-controlled namespace could signal, delete, and reset workflows or activities in a victim namespace on the same cluster. Exploitation requires the attacker to know or guess specific victim workflow ID(s) and, for signal operations, signal names. This was due to a bug introduced in Temporal Server v1.29.0 which inadvertently allowed an attacker to control the namespace name value instead of using the server's own trusted name value within the batch activity code. The batch activity validated the namespace ID but did not cross-check the namespace name against the worker's bound namespace, allowing the per-namespace worker's privileged credentials to operate on an arbitrary namespace. Exploitation requires a server configuration where internal components have cross-namespace authorization, such as deployment of the internal-frontend service or equivalent TLS-based authorization for internal identities. This vulnerability also impacted Temporal Cloud when the attacker and victim namespaces were on the same cell, with the same preconditions as self-hosted clusters.

Timeline

1. Apr 1, 2026, 5:49 PM UTCCVE published
2. Apr 1, 2026, 6:23 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Apr 1, 2026, 6:24 PM UTCRecord last updated

Affected versions

• temporal

  From 1.29.0 · fixed in 1.29.5; From 1.30.0 · fixed in 1.30.3

• go.temporal.io/serverGo

  fixed in 1.29.5; From 1.30.0-143.0 · fixed in 1.30.3

• go.temporal.io/serverGo

  From 1.30.0-143.0 · fixed in 1.30.3

• go.temporal.io/serverGo

  fixed in 1.29.5

References 2