ExecuteMultiOperation Namespace Policy Bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Temporal | Temporal | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Temporal | Temporal | — |
Vendor Workaround
Set frontend.enableExecuteMultiOperation to false
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-p2gr-hm8g-q772 | Temporal has a namespace policy bypass allowing requests to be authorized for incorrect contexts |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.426% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Temporal
Temporal temporal |
|
| Vendors & Products |
Temporal
Temporal temporal |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | When frontend.enableExecuteMultiOperation is enabled, the server can apply namespace-scoped validation and feature gates for the embedded StartWorkflowExecutionRequest using its Namespace field rather than the outer, authorized ExecuteMultiOperationRequest.Namespace. This allows a caller authorized for one namespace to bypass that namespace's limits/policies by setting the embedded start request's namespace to a different namespace. The workflow is still created in the outer (authorized) namespace; only validation/gating is performed under the wrong namespace context. This issue affects Temporal: from 1.24.0 through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2. | |
| Title | ExecuteMultiOperation Namespace Policy Bypass | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV4_0
|