Cross Namespace Commands Authorization Bypass
Temporal
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| go.temporal.io/server Go |
|
|
Temporal
| Product | Affected | Fixed in |
|---|---|---|
| go.temporal.io/server Go |
|
|
When system.enableCrossNamespaceCommands is enabled (on by default), the Temporal server permits certain workflow task commands (e.g. StartChildWorkflowExecution, SignalExternalWorkflowExecution, RequestCancelExternalWorkflowExecution) to target a different namespace than the namespace authorized at the gRPC boundary. The frontend authorizes RespondWorkflowTaskCompleted based on the outer request namespace, but the history service later resolves and executes the command using the namespace embedded in command attributes without authorizing the caller for that target namespace. This can allow a worker authorized for one namespace to create, signal, or cancel workflows in another namespace. This issue affects Temporal: through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2.
From the CVE record · Temporal
When system.enableCrossNamespaceCommands is enabled (the default), Temporal authorizes a workflow task completion against its outer namespace but does not authorize the namespace specified in certain commands. A worker authorized for one namespace can create, signal, or cancel workflows in another namespace through those commands.
Operators running affected versions of the Go package go.temporal.io/server, including versions through 1.29.1, should check their deployments.