Authorization Bypass Through User-Controlled Key Affecting github.com/temporalio/temporal/service/history/api/getworkflowexecutionhistoryreverse package, versions >=1.0.0 <1.29.7>=1.30.0 <1.30.7>=1.31.0 <1.31.3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Authorization Bypass Through User-Controlled Key vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMTEMPORALIOTEMPORALSERVICEHISTORYAPIGETWORKFLOWEXECUTIONHISTORYREVERSE-22500070
- published12 Nov 2026
- disclosed9 Nov 2026
- creditUnknown
Introduced: 9 Nov 2026
NewCVE-2026-87857 Â (opens in a new tab)How to fix?
Upgrade github.com/temporalio/temporal/service/history/api/getworkflowexecutionhistoryreverse to version 1.29.7, 1.30.7, 1.31.3 or higher.
Overview
Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key via the GetWorkflowExecutionHistory and GetWorkflowExecutionHistoryReverse handlers in the History service. An authenticated caller with read access to one namespace can replay a genuine, non-final pagination token issued for a workflow in another namespace in a request for the accessible namespace, provided the supplied workflow ID maps to the same History shard; the request does not need to name an existing workflow. The handlers use the token’s branch to select history without binding it to the requested namespace or workflow, exposing the other workflow’s history; because the token is unauthenticated, the caller can also alter its event range and clear its persistence cursor to retrieve later events even after access to that namespace is revoked.