CVE-2025-14986: Temporal has a namespace policy bypass allowing requests to be authorized for incorrect contexts
(updated )
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.
References
- github.com/advisories/GHSA-p2gr-hm8g-q772
- github.com/temporalio/temporal
- github.com/temporalio/temporal/pull/8839
- github.com/temporalio/temporal/releases/tag/v1.27.4
- github.com/temporalio/temporal/releases/tag/v1.28.2
- github.com/temporalio/temporal/releases/tag/v1.29.2
- nvd.nist.gov/vuln/detail/CVE-2025-14986
Code Behaviors & Features
Detect and mitigate CVE-2025-14986 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →