This issue affects Temporal: from 1.24.0 through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2.
Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
Set frontend.enableExecuteMultiOperation to false
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-p2gr-hm8g-q772 | Temporal has a namespace policy bypass allowing requests to be authorized for incorrect contexts |
Mon, 05 Jan 2026 10:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Temporal
Temporal temporal |
|
| Vendors & Products |
Temporal
Temporal temporal |
Fri, 02 Jan 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 30 Dec 2025 20:30:00 +0000
| 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
|
Status: PUBLISHED
Assigner: Temporal
Published:
Updated: 2026-01-02T15:31:02.796Z
Reserved: 2025-12-19T19:18:54.548Z
Link: CVE-2025-14986
Updated: 2026-01-02T15:30:59.515Z
Status : Deferred
Published: 2025-12-30T21:15:42.773
Modified: 2026-04-15T00:35:42.020
Link: CVE-2025-14986
No data.
OpenCVE Enrichment
Updated: 2026-01-05T10:19:38Z
Github GHSA