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.
{
"cna_assigner": "Temporal",
"cwe_ids": [
"CWE-863"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/14xxx/CVE-2025-14986.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "1.24.0"
},
{
"last_affected": "1.29.1"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "1.24.0"
},
{
"last_affected": "1.28.1"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "1.24.0"
},
{
"last_affected": "1.27.3"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"original_tag": "v1.27.4",
"range": [
{
"fixed": "3162b75c656c0c38d43ff834c9ddc6fffc6abc73"
}
],
"source": "REFERENCES_TAG"
},
{
"original_tag": "v1.28.2",
"range": [
{
"fixed": "09d90574e0f0ca65c33e19dc32a32f63579fc229"
}
],
"source": "REFERENCES_TAG"
},
{
"original_tag": "v1.29.2",
"range": [
{
"fixed": "dfc3c9ad65407c0f81e99c2db2d33fa0a52e8633"
}
],
"source": "REFERENCES_TAG"
}
]
}