cve.bz

CVE-2026-104355 temporal technologies, inc. temporal server: Incorrect Authorization

7.0 highEPSS 0.4%

High (7.0) in temporal technologies, inc. temporal server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.0 high
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
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-104355 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104355?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104355?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-104355 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • temporal technologies, inc.:temporal server

Versions

From the CNA's record in the CVE List.

ProductAffected
Temporal Technologies, Inc. Temporal Serverfrom 1.0.0 through 1.29.7
Temporal Technologies, Inc. Temporal Serverfrom 1.30.0 before 1.30.8
Temporal Technologies, Inc. Temporal Serverfrom 1.31.0 before 1.31.4
Temporal Technologies, Inc. Temporal Serverfrom 1.32.0 before 1.32.1

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate severity flaw was found in the Temporal Server component shipped in Red Hat Ansible Automation Orchestrator (automation-orchestrator-temporal-rhel9). In a multi-cluster Temporal deployment, the receiving cluster fails to verify that inbound namespace replication tasks apply only to global namespaces. An attacker who controls or compromises a registered peer cluster whose connection an administrator has enabled can send replication updates that overwrite the configuration of local namespaces, including state, owner, retention, archival settings, and active cluster assignment, without holding any credential on the receiving cluster. For example, marking a namespace Deprecated, making the peer its active cluster, or shortening its retention causes new workflow starts in that namespace to fail, resulting in denial of service. Deployments with no remote cluster registered with connection enabled are not exposed. Red Hat rates this flaw Moderate severity (CVSS 5.5, AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:L), lower than the upstream CVSS 4.0 score of 7.0 (Important), primarily because exploitation requires control of an administrator-registered peer cluster, a high-privilege precondition within the multi-cluster trust model. The fix for the affected Red Hat product is deferred because the impact is Moderate with a CVSS score below 7.0; the residual risk is limited to multi-cluster deployments that use replication with a compromised or attacker-controlled connected peer.

Red Hat's mitigation

A workaround is available: administrators of multi-cluster Temporal deployments can eliminate the exposure by removing remote cluster registrations or disabling connections to remote clusters, since a cluster with no remote cluster registered with connection enabled is not vulnerable to this issue. Restricting network access so that only trusted, uncompromised peers can communicate with the cluster also reduces risk. Note that disabling remote cluster connections comes at the cost of cross-cluster replication functionality. Alternatively, upgrading Temporal Server to an upstream release that contains the fix addresses the issue.

ProductPackageStateAdvisory
Ansible Automation Orchestrator 2026ansible-automation-platform/automation-orchestrator-temporal-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-104355.

References

Check your stackJSON