CVE-2025-14987 — server
Fix: temporalio/temporal@b292a32CVE-2025-14987 is a CWE-863 vulnerability in go.temporal.io/server. A fix is available for go.temporal.io/server — see the affected versions and patch details below.
Cross Namespace Commands Authorization Bypass
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-14987.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
go.temporal.io/server🐹go.temporal.io/server🐹go.temporal.io/server🐹go.temporal.io/serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | go.temporal.io/server | all versions | 1.27.4go get go.temporal.io/server@v1.27.4 |
| 🐹Go | go.temporal.io/server | ≥ 1.28.0&&< 1.28.2 | 1.28.2go get go.temporal.io/server@v1.28.2 |
| 🐹Go | go.temporal.io/server | ≥ 1.29.0&&< 1.29.2 | 1.29.2go get go.temporal.io/server@v1.29.2 |
| 🐹Go | go.temporal.io/server | ≥ 1.29.0-0&&< 1.29.0-135.0.0.20251218190115-b292a32bacdf | 1.29.0-135.0.0.20251218190115-b292a32bacdfgo get go.temporal.io/server@v1.29.0-135.0.0.20251218190115-b292a32bacdf |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.temporal.io/server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update go.temporal.io/server to 1.27.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-14987 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-14987 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-14987. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-14987 in your dependencies?
O3 Security finds CVE-2025-14987 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.