Advisory

GHSA-xpg8-3hhp-p7w8

Also known as: CVE-2026-5199, GO-2026-5766

Summary

Temporal Server: attacker-controlled namespace could signal, delete, and reset workflows or activities in a victim namespace on the same cluster

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-04-01 18:36 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

go.temporal.io/server

Go · All systems

Affected

  • introduced 1.30.0-143.0, fixed 1.30.3 (semver)

Fixed versions

1.30.3

Fix

go.temporal.io/server

Go · All systems

Affected

  • introduced 0, fixed 1.29.5 (semver)

Fixed versions

1.29.5

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences