Authorization bypass in Temporal Server workflow history pagination
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
Temporal Server 1.0.0 through 1.29.7, 1.30.0 before 1.30.7 and 1.31.0 before 1.31.3 do not bind a workflow-history pagination token to the namespace and workflow named in the request (CWE-639). An authenticated caller with read permission on one namespace who holds an earlier continuation token from another namespace can read that namespace's workflow history. The token is unauthenticated, so its holder can also widen the event range.
Written with Claude Haiku 5.5 from the sources below · 2026-11-09
Description from the CNA
Temporal Server does not bind a workflow-history pagination token to the namespace and workflow named in the request that presents it. GetWorkflowExecutionHistory and GetWorkflowExecutionHistoryReverse authorize the caller against the namespace in the request, then select history from the branch recorded inside the caller-supplied next_page_token. The normal history continuation carries a run identifier, event bounds, a persistence cursor, and a branch token, but no namespace or workflow identity, and it is serialized as unauthenticated protobuf bytes. An authenticated caller holding read permission on one namespace, together with a genuine non-final continuation issued earlier for a workflow in a second namespace, can submit that continuation with a request naming the first namespace and receive the second namespace's workflow history, provided the supplied workflow identifier selects the same History shard as the continuation's branch. No workflow with the supplied identifier needs to exist. Because the token is unauthenticated, a holder can also advance its event range and clear its persistence cursor, which returns history events created after that caller's current credential no longer granted access to the continuation's namespace. Determining exposure is a version question rather than a configuration question: every release listed as affected omits the binding check on the forward history path, and on the reverse history path in releases from 1.16.0, which introduced GetWorkflowExecutionHistoryReverse; no setting in an affected release restores it, and affected releases emit no metric or log for the condition, so their telemetry provides no detection. Fixed releases add the check and, when a page token's branch token is not the requested execution's current branch token, record the counter pagination_token_branch_mismatch tagged with namespace and reason and write a History-service warning log reading "Pagination branch token is not the execution's current branch token" with the fields wf-namespace, wf-id, wf-run-id, reason, wf-branch-token, and wf-request-branch-token. Search History warning logs for that message, or for reason=foreign_branch, which denotes a branch token the requested execution never recorded and is not expected in normal operation; reason=non_current_branch denotes a retained but superseded branch of the same execution and can occur legitimately after conflict resolution or failover. A foreign_branch record does not by itself prove the read was refused, because the counter and log are emitted before the enforcement decision and therefore appear both when the check rejects the request and when history.enablePaginationTokenBranchValidationShadowMode is enabled and the read is served; confirm refusal from the gRPC response, which is InvalidArgument carrying a CurrentBranchChangedFailure detail. The metric and log are tagged with the requesting namespace, not the namespace whose history the token selects, so a foreign_branch alert does not name the exposed namespace. The issue does not provide unauthenticated access, construction of a usable continuation from public workflow identifiers, enumeration of workflows for which the caller holds no continuation, or any modification of workflow state.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Temporal Technologies, Inc. | Temporal Server | 1.0.0 – 1.29.7; 1.30.0 to before 1.30.7; 1.31.0 to before 1.31.3 | 1.30.7, 1.31.3 | Patch available | CNA |
- Temporal Server VendorTemporal Technologies, Inc. Affected 1.0.0 – 1.29.7; 1.30.0 to before 1.30.7; 1.31.0 to before 1.31.3 Fixed in 1.30.7, 1.31.3 Patch available CNA
Remediation
Upgrade to Temporal Server 1.30.7 or 1.31.3, which fix the flaw. The sources list no fixed version for Temporal Server releases through 1.29.7.
Written with Claude Haiku 5.5 from the sources below · 2026-11-09
- Fix · CNA Temporal Server (Temporal Technologies, Inc.) Fixed in 1.30.7, 1.31.3
Timeline
- 2026-11-09 Threatist record created from CVE-2026-87857
- 2026-11-09 Alias added: GHSA-fqqw-cv9m-h3p6
- 2026-11-12 CISA SSVC decision points changed
References
Patch 8
More Temporal Technologies, Inc. vulnerabilities
- TI-2026-63861 s2s-proxy accepts untrusted client certificates CVSS 4.0CRITICAL 9.3
- TI-2026-46800 temporalio/tchannel-go zero-chunk call fragment causes process termination CVSS 4.0HIGH 8.7
- TI-2026-46799 temporalio/tchannel-go malformed checksum type causes process termination CVSS 4.0HIGH 8.7
- TI-2026-46801 temporalio/ringpop-go fails to enforce configured label limits on inbound membership gossip CVSS 4.0HIGH 8.7
- TI-2026-13897 temporalio/sqlparser malformed MySQL version comments can cause a panic CVSS 4.0HIGH 8.7
- TI-2026-84119 Temporal Server k8s compute provider lets callers run host commands CVSS 4.0HIGH 8.7
Sources
- CVE-2026-87857 · CVE Program
- CVE-2026-87857 · NVD
- FIRST EPSS
- GHSA-fqqw-cv9m-h3p6 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences