# CVE-2025-14986: ExecuteMultiOperation Namespace Policy Bypass

> Attackers can bypass namespace-specific policies and limits in Temporal by exploiting a validation flaw in multi-operation requests when a specific feature is enabled.

- **Severity:** Low 1.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U/S:N/AU:Y/R:U/RE:L/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 2 Jan 2026
- **Also known as:** CLEANSTART-2026-NH98703, CLEANSTART-2026-SU00653, GHSA-p2gr-hm8g-q772, GO-2025-4272

## What is CVE-2025-14986?

CVE-2025-14986 is a low-severity missing authorization vulnerability in Temporal, published on 30 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-14986?

7 open source packages ship an affected version, including go.temporal.io/server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `go.temporal.io/server` | Go | From 1.24.0 | 1.27.4, 1.28.2, 1.29.2 |
| `go.temporal.io/server` | Go | From 1.24.0 | 1.27.4 |
| `go.temporal.io/server` | Go | From 1.24.0 | 1.27.4 |
| `go.temporal.io/server` | Go | From 1.28.0 | 1.28.2 |
| `go.temporal.io/server` | Go | From 1.28.0 | 1.28.2 |
| `go.temporal.io/server` | Go | From 1.29.0 | 1.29.2 |
| `go.temporal.io/server` | Go | From 1.29.0 | 1.29.2 |

## How do I fix CVE-2025-14986?

Upgrade go.temporal.io/server to a fixed version for your release line: 1.27.4, 1.28.2 or 1.29.2.

## Is CVE-2025-14986 being exploited?

There is no known exploitation of CVE-2025-14986 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14986 and fix it if it is affected.

What it is: CVE-2025-14986 is a low-severity missing authorization vulnerability in Temporal, published on 30 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14986 in the wild and no public exploit code.

Affected packages and fixed versions:
- go.temporal.io/server (Go): affected from 1.24.0; fixed in 1.27.4, 1.28.2, 1.29.2
- go.temporal.io/server (Go): affected from 1.24.0; fixed in 1.27.4
- go.temporal.io/server (Go): affected from 1.24.0; fixed in 1.27.4
- go.temporal.io/server (Go): affected from 1.28.0; fixed in 1.28.2
- go.temporal.io/server (Go): affected from 1.28.0; fixed in 1.28.2
- go.temporal.io/server (Go): affected from 1.29.0; fixed in 1.29.2
- go.temporal.io/server (Go): affected from 1.29.0; fixed in 1.29.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14986/ (Markdown: https://insights.sbomify.com/CVE-2025-14986/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14986
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14986
- OSV: https://osv.dev/vulnerability/CVE-2025-14986

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14986/
Summaries are generated and may contain mistakes; the official description above is the record.