CVE-2026-5199: CWE-639 Authorization bypass through User-Controlled key in Temporal Technologies, Inc. temporal
A writer role user in an attacker-controlled namespace could signal, delete, and reset workflows or activities in a victim namespace on the same cluster. Exploitation requires the attacker to know or guess specific victim workflow ID(s) and, for signal operations, signal names. This was due to a bug introduced in Temporal Server v1.29.0 which inadvertently allowed an attacker to control the namespace name value instead of using the server's own trusted name value within the batch activity code. The batch activity validated the namespace ID but did not cross-check the namespace name against the worker's bound namespace, allowing the per-namespace worker's privileged credentials to operate on an arbitrary namespace. Exploitation requires a server configuration where internal components have cross-namespace authorization, such as deployment of the internal-frontend service or equivalent TLS-based authorization for internal identities. This vulnerability also impacted Temporal Cloud when the attacker and victim namespaces were on the same cell, with the same preconditions as self-hosted clusters.
AI Analysis
Technical Summary
CVE-2026-5199 is a security vulnerability classified under CWE-639 (Authorization Bypass Through User-Controlled Key) affecting Temporal Technologies, Inc.'s Temporal Server versions 1.29.0 and 1.30.0. The flaw arises from a logic error introduced in version 1.29.0 where the batch activity code incorrectly used a namespace name value controlled by the user rather than the server's trusted namespace name. This allowed a user with a writer role in an attacker-controlled namespace to perform privileged operations such as signaling, deleting, and resetting workflows or activities in victim namespaces residing on the same cluster. The vulnerability exploits the fact that while the batch activity validated the namespace ID, it failed to cross-check the namespace name against the worker's bound namespace, thereby granting the per-namespace worker's privileged credentials the ability to operate on arbitrary namespaces. Exploitation requires the attacker to know or guess specific victim workflow IDs and signal names, and depends on server configurations that permit cross-namespace authorization among internal components, such as the deployment of the internal-frontend service or equivalent TLS-based authorization for internal identities. This vulnerability also impacts Temporal Cloud when attacker and victim namespaces share the same cell under similar conditions. Although the CVSS 4.0 score is low (2.3), reflecting the need for some privileges and knowledge, the flaw represents a significant authorization bypass that could lead to unauthorized workflow manipulation. No public exploits have been reported to date, and no patches are linked in the provided data.
Potential Impact
The primary impact of CVE-2026-5199 is unauthorized manipulation of workflows and activities across namespaces within the same Temporal cluster. An attacker with writer role privileges in one namespace can signal, delete, or reset workflows in other victim namespaces, potentially disrupting business processes, causing data loss, or triggering unintended operations. This could lead to integrity and availability issues within affected Temporal deployments. Organizations relying on Temporal for critical workflow orchestration may face operational disruptions, especially if sensitive or high-value workflows are targeted. The impact is somewhat mitigated by the requirement for the attacker to have writer role access in an attacker-controlled namespace and to know or guess victim workflow IDs and signal names. However, in multi-tenant or shared cluster environments, or where internal components allow cross-namespace authorization, the risk is elevated. Temporal Cloud customers sharing cells are also at risk under these conditions. While the CVSS score is low, the potential for unauthorized cross-namespace operations can have serious consequences for workflow integrity and availability.
Mitigation Recommendations
To mitigate CVE-2026-5199, organizations should upgrade Temporal Server to versions beyond 1.30.0 once patches are released, as the vulnerability was introduced in 1.29.0 and persists in 1.30.0. Until patches are available, administrators should review and restrict server configurations that allow cross-namespace authorization among internal components, such as disabling or tightly controlling the internal-frontend service or equivalent TLS-based authorization mechanisms. Implement strict namespace isolation policies and limit writer role assignments to trusted users only. Monitor workflow operations for unusual signaling, deletion, or reset activities that could indicate exploitation attempts. Employ network segmentation and access controls to reduce the risk of unauthorized namespace access. For Temporal Cloud users, coordinate with the service provider to understand cell-sharing configurations and request mitigation or isolation if possible. Additionally, enforce strong workflow ID and signal name management to reduce the likelihood of guessing or discovery by attackers. Regularly audit namespace permissions and internal service configurations to ensure adherence to the principle of least privilege.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, Japan, France, Netherlands, India, Singapore
CVE-2026-5199: CWE-639 Authorization bypass through User-Controlled key in Temporal Technologies, Inc. temporal
Description
A writer role user in an attacker-controlled namespace could signal, delete, and reset workflows or activities in a victim namespace on the same cluster. Exploitation requires the attacker to know or guess specific victim workflow ID(s) and, for signal operations, signal names. This was due to a bug introduced in Temporal Server v1.29.0 which inadvertently allowed an attacker to control the namespace name value instead of using the server's own trusted name value within the batch activity code. The batch activity validated the namespace ID but did not cross-check the namespace name against the worker's bound namespace, allowing the per-namespace worker's privileged credentials to operate on an arbitrary namespace. Exploitation requires a server configuration where internal components have cross-namespace authorization, such as deployment of the internal-frontend service or equivalent TLS-based authorization for internal identities. This vulnerability also impacted Temporal Cloud when the attacker and victim namespaces were on the same cell, with the same preconditions as self-hosted clusters.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-5199 is a security vulnerability classified under CWE-639 (Authorization Bypass Through User-Controlled Key) affecting Temporal Technologies, Inc.'s Temporal Server versions 1.29.0 and 1.30.0. The flaw arises from a logic error introduced in version 1.29.0 where the batch activity code incorrectly used a namespace name value controlled by the user rather than the server's trusted namespace name. This allowed a user with a writer role in an attacker-controlled namespace to perform privileged operations such as signaling, deleting, and resetting workflows or activities in victim namespaces residing on the same cluster. The vulnerability exploits the fact that while the batch activity validated the namespace ID, it failed to cross-check the namespace name against the worker's bound namespace, thereby granting the per-namespace worker's privileged credentials the ability to operate on arbitrary namespaces. Exploitation requires the attacker to know or guess specific victim workflow IDs and signal names, and depends on server configurations that permit cross-namespace authorization among internal components, such as the deployment of the internal-frontend service or equivalent TLS-based authorization for internal identities. This vulnerability also impacts Temporal Cloud when attacker and victim namespaces share the same cell under similar conditions. Although the CVSS 4.0 score is low (2.3), reflecting the need for some privileges and knowledge, the flaw represents a significant authorization bypass that could lead to unauthorized workflow manipulation. No public exploits have been reported to date, and no patches are linked in the provided data.
Potential Impact
The primary impact of CVE-2026-5199 is unauthorized manipulation of workflows and activities across namespaces within the same Temporal cluster. An attacker with writer role privileges in one namespace can signal, delete, or reset workflows in other victim namespaces, potentially disrupting business processes, causing data loss, or triggering unintended operations. This could lead to integrity and availability issues within affected Temporal deployments. Organizations relying on Temporal for critical workflow orchestration may face operational disruptions, especially if sensitive or high-value workflows are targeted. The impact is somewhat mitigated by the requirement for the attacker to have writer role access in an attacker-controlled namespace and to know or guess victim workflow IDs and signal names. However, in multi-tenant or shared cluster environments, or where internal components allow cross-namespace authorization, the risk is elevated. Temporal Cloud customers sharing cells are also at risk under these conditions. While the CVSS score is low, the potential for unauthorized cross-namespace operations can have serious consequences for workflow integrity and availability.
Mitigation Recommendations
To mitigate CVE-2026-5199, organizations should upgrade Temporal Server to versions beyond 1.30.0 once patches are released, as the vulnerability was introduced in 1.29.0 and persists in 1.30.0. Until patches are available, administrators should review and restrict server configurations that allow cross-namespace authorization among internal components, such as disabling or tightly controlling the internal-frontend service or equivalent TLS-based authorization mechanisms. Implement strict namespace isolation policies and limit writer role assignments to trusted users only. Monitor workflow operations for unusual signaling, deletion, or reset activities that could indicate exploitation attempts. Employ network segmentation and access controls to reduce the risk of unauthorized namespace access. For Temporal Cloud users, coordinate with the service provider to understand cell-sharing configurations and request mitigation or isolation if possible. Additionally, enforce strong workflow ID and signal name management to reduce the likelihood of guessing or discovery by attackers. Regularly audit namespace permissions and internal service configurations to ensure adherence to the principle of least privilege.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Temporal
- Date Reserved
- 2026-03-30T23:48:01.861Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69cd5f13e6bfc5ba1de6e545
Added to database: 4/1/2026, 6:08:19 PM
Last enriched: 4/1/2026, 6:25:58 PM
Last updated: 4/6/2026, 8:23:26 AM
Views: 20
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.