CVE-2025-14986
Namespace Validation Bypass in Temporal ExecuteMultiOperation Feature
Publication date: 2025-12-30
Last updated on: 2025-12-30
Assigner: Temporal Technologies Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| temporal | temporal | 1.29.1 |
| temporal | temporal | 1.29.2 |
| temporal | temporal | 1.25.0 |
| temporal | temporal | 1.26.0 |
| temporal | temporal | 1.24.0 |
| temporal | temporal | 1.28.2 |
| temporal | temporal | 1.27.4 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs when the feature frontend.enableExecuteMultiOperation is enabled in Temporal server versions 1.24.0 through 1.29.1. The server incorrectly applies namespace-scoped validation and feature gates based on the Namespace field of an embedded StartWorkflowExecutionRequest rather than the outer, authorized ExecuteMultiOperationRequest.Namespace. This allows a caller authorized for one namespace to bypass that namespace's limits and policies by setting the embedded start request's namespace to a different namespace. Although the workflow is created in the authorized outer namespace, validation and gating are performed under the wrong namespace context, potentially allowing policy circumvention.
How can this vulnerability impact me? :
This vulnerability can allow an attacker or unauthorized user who has permission in one namespace to bypass the limits and policies of that namespace by manipulating the embedded start request's namespace. This could lead to unauthorized actions or workflows being initiated that circumvent intended namespace restrictions, potentially undermining security controls and operational policies within the Temporal server environment.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade your Temporal server to a fixed version that includes patches for CVE-2025-14986. The fixed versions are 1.27.4, 1.28.2, or 1.29.2. Applying these updates will address the security issue related to namespace validation bypass. [1, 2, 3]