Cross Namespace Commands Authorization Bypass
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.27.4, 1.28.2, 1.29.2, 1.29.0-135.0.0.20251218190115-b292a32bacdf
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- temporal
through 1.29.1; through 1.28.1; through 1.27.3
- go.temporal.io/serverGo
fixed in 1.27.4
- go.temporal.io/serverGo
From 1.28.0 · fixed in 1.28.2
- go.temporal.io/serverGo
From 1.29.0 · fixed in 1.29.2
- go.temporal.io/serverGo
From 1.29.0-0 · fixed in 1.29.0-135.0.0.20251218190115-b292a32bacdf
- go.temporal.io/serverGo
fixed in 1.27.4; From 1.28.0 · fixed in 1.28.2; From 1.29.0 · fixed in 1.29.2