ExecuteMultiOperation Namespace Policy Bypass
cve-program · CVE-2025-14986
PublishedWhen 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.
Read the publisher's advisoryeuvd · EUVD-2025-205854
PublishedWhen 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.
Read the publisher's advisorynvd · CVE-2025-14986
PublishedWhen 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.
Read the publisher's advisoryosv · GHSA-p2gr-hm8g-q772
PublishedWhen 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.
Read the publisher's advisoryosv · GO-2025-4272
PublishedTemporal has a namespace policy bypass allowing requests to be authorized for incorrect contexts in go.temporal.io/server
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2025-14986 · CVE overview and exploitation status
cve-program · CVE-2025-14986
- https://github.com/temporalio/temporal/releases/tag/v1.27.4
- https://github.com/temporalio/temporal/releases/tag/v1.28.2
- https://github.com/temporalio/temporal/releases/tag/v1.29.2
euvd · EUVD-2025-205854
- https://github.com/temporalio/temporal/releases/tag/v1.27.4
- https://github.com/temporalio/temporal/releases/tag/v1.28.2
- https://github.com/temporalio/temporal/releases/tag/v1.29.2
nvd · CVE-2025-14986
- https://github.com/temporalio/temporal/releases/tag/v1.27.4
- https://github.com/temporalio/temporal/releases/tag/v1.28.2
- https://github.com/temporalio/temporal/releases/tag/v1.29.2
osv · GHSA-p2gr-hm8g-q772
- https://nvd.nist.gov/vuln/detail/CVE-2025-14986
- https://github.com/temporalio/temporal/pull/8839
- https://github.com/temporalio/temporal
- https://github.com/temporalio/temporal/releases/tag/v1.27.4
- https://github.com/temporalio/temporal/releases/tag/v1.28.2
- https://github.com/temporalio/temporal/releases/tag/v1.29.2
osv · GO-2025-4272
- https://github.com/advisories/GHSA-p2gr-hm8g-q772
- https://nvd.nist.gov/vuln/detail/CVE-2025-14986
- https://github.com/temporalio/temporal/pull/8839
- https://github.com/temporalio/temporal/releases/tag/v1.27.4
- https://github.com/temporalio/temporal/releases/tag/v1.28.2
- https://github.com/temporalio/temporal/releases/tag/v1.29.2
Related changes
Linked by CVE identifierNo related changes are available here.