go.temporal.io/server
Affected
- introduced
1.24.0, fixed1.27.4(semver)
Fixed versions
1.27.4
Fix
- Fixed version
1.27.4go get go.temporal.io/[email protected]
Advisory
Also known as: CVE-2025-14986, GO-2025-4272
Temporal has a namespace policy bypass allowing requests to be authorized for incorrect contexts
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.
Low Basis: The source's own band: LOW
1.24.0, fixed 1.27.4 (semver)1.27.4
1.27.4go get go.temporal.io/[email protected]1.28.0, fixed 1.28.2 (semver)1.28.2
1.28.2go get go.temporal.io/[email protected]1.29.0, fixed 1.29.2 (semver)1.29.2
1.29.2go get go.temporal.io/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0