NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2025-14986: Temporal has a namespace policy bypass allowing requests to be authorized for incorrect contexts

lowCVSS 4.0 1.3GHSA-p2gr-hm8g-q772

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.

Published Dec 30, 2025 · Updated Dec 31, 2025

Affected packages

go.temporal.io/server

Ecosystem
Go
Affected
>= 1.24.0, < 1.27.4
Fixed in
1.27.4
Check
go list -m go.temporal.io/server

go.temporal.io/server

Ecosystem
Go
Affected
>= 1.28.0, < 1.28.2
Fixed in
1.28.2
Check
go list -m go.temporal.io/server

go.temporal.io/server

Ecosystem
Go
Affected
>= 1.29.0, < 1.29.2
Fixed in
1.29.2
Check
go list -m go.temporal.io/server

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries