CVE-2026-104355Temporal Server applies inbound namespace replication from a connected peer cluster to local namespaces
Updated under an hour ago ()
Does this affect you?
It affects Temporal Technologies, Inc. Temporal Server. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.36%, higher than 28% of scored CVEs.
Do this next
Free account, 1 product
A connected peer cluster can modify a Temporal Server cluster's local namespaces, which are never replicated to that peer, because the receiving cluster applies inbound namespace replication updates to them. In a multi-cluster deployment, each cluster pulls replication tasks from the remote clusters an administrator has registered with connection enabled; the sending side excludes local namespaces, but the receiving side does not apply the same rule. When an inbound task names an existing namespace, the server checks at most that the namespace identifiers match, then overwrites its state, description, owner, retention, archival settings, and cluster list, and its active cluster when the task carries a higher failover version, without checking that the namespace is global. A party that controls a registered peer's replies, by operating or compromising it, can therefore change any local namespace whose name and identifier it can supply, without any credential on the receiving cluster: for example, marking it Deprecated, making the peer its active cluster, and shortening its retention, after which new Workflow starts in that namespace fail. Local namespaces include the built-in temporal-system namespace. Namespace metadata the History service refreshes from the peer while processing its history replication tasks passes through the same logic. A cluster with no remote cluster registered with connection enabled is not exposed.
- CVSS
- 7.0 HIGH (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
- Weakness (CWE)
- CWE-863
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.36% (percentile 28)
- Assigned by
- Temporal
- NVD analysis
- Awaiting Analysis
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 12, 2026
Affected products
Temporal Technologies, Inc. Temporal Server temporal:temporal | from 0.0.0 before 1.0.0 status unknown; from 1.0.0 through 1.29.7; from 1.30.0 before 1.30.8; from 1.31.0 before 1.31.4; from 1.32.0 before 1.32.1 | CNA record |
References
- https://github.com/temporalio/temporal/blob/v1.0.0/common/namespace/replicationTaskExecutor.go#L191-L260product
- https://github.com/temporalio/temporal/pull/12323patch
- https://github.com/temporalio/temporal/commit/f2b571e2eee8a9143fbc4711f3db8b5a37146b3bpatch
- https://github.com/temporalio/temporal/pull/12328patch
- https://github.com/temporalio/temporal/pull/12329patch
- https://github.com/temporalio/temporal/pull/12330patch
- https://github.com/temporalio/temporal/releases/tag/v1.30.8release-notes
- https://github.com/temporalio/temporal/releases/tag/v1.31.4release-notes
- https://github.com/temporalio/temporal/releases/tag/v1.32.1release-notes
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.