Home

Description

When system.enableCrossNamespaceCommands is enabled (on by default), the Temporal server permits certain workflow task commands (e.g. StartChildWorkflowExecution, SignalExternalWorkflowExecution, RequestCancelExternalWorkflowExecution) to target a different namespace than the namespace authorized at the gRPC boundary. The frontend authorizes RespondWorkflowTaskCompleted based on the outer request namespace, but the history service later resolves and executes the command using the namespace embedded in command attributes without authorizing the caller for that target namespace. This can allow a worker authorized for one namespace to create, signal, or cancel workflows in another namespace. This issue affects Temporal: through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2.

PUBLISHED Reserved 2025-12-19 | Published 2025-12-30 | Updated 2025-12-30 | Assigner Temporal




MEDIUM: 5.3CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L

Problem types

CWE-863 Incorrect Authorization

Product status

Default status
unaffected

Any version
affected

Any version
affected

Any version
affected

References

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

cve.org (CVE-2025-14987)

nvd.nist.gov (CVE-2025-14987)

Download JSON

Data based on CVE®. Copyright © 1999-2025, The MITRE Corporation. All rights reserved.