CVE-2025-14986: ExecuteMultiOperation Namespace Policy Bypass
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-14986?
CVE-2025-14986 is considered a high-severity vulnerability that affects specific versions of Temporal.
How do I fix CVE-2025-14986?
To mitigate CVE-2025-14986, update to Temporal versions 1.29.2 or later, or apply relevant security patches.
What versions of Temporal are affected by CVE-2025-14986?
CVE-2025-14986 affects Temporal versions from 1.24.0 to 1.29.1, as well as those below version 1.27.4.
What is the impact of CVE-2025-14986?
The impact of CVE-2025-14986 allows unauthorized namespace-scoped access when executing multi-operation requests.
Is CVE-2025-14986 exploitable?
Yes, CVE-2025-14986 is exploitable if the 'frontend.enableExecuteMultiOperation' feature is enabled on affected Temporal versions.