Summary
Temporal does not enforce authentication and authorization for the streaming AdminService/StreamWorkflowReplicationMessages endpoint
The frontend gRPC server's streaming interceptor chain did not include the authorization interceptor. When a ClaimMapper and Authorizer are configured, unary RPCs enforce authentication and authorization, but the streaming AdminService/StreamWorkflowReplicationMessages endpoint accepted requests without credentials. This endpoint is registered on the same port as WorkflowService and cannot be disabled independently. An attacker with network access to the frontend port could open the replication stream without authentication. Data exfiltration is possible, but only when a configured replication target is correctly configured and the attacker has knowledge of the cluster configuration, as the history service validates cluster IDs and peer membership before returning replication data.
Temporal Cloud is not affected.
Impact
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
go.temporal.io/server to 1.28.4 or later; go.temporal.io/server to 1.29.6 or later; go.temporal.io/server to 1.30.4 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-5724? CVE-2026-5724 is a medium-severity missing authentication for critical function vulnerability in go.temporal.io/server (go), affecting versions < 1.28.4. It is fixed in 1.28.4, 1.29.6, 1.30.4. A critical operation is accessible without requiring any authentication.
- Which versions of go.temporal.io/server are affected by CVE-2026-5724? go.temporal.io/server (go) versions < 1.28.4 is affected.
- Is there a fix for CVE-2026-5724? Yes. CVE-2026-5724 is fixed in 1.28.4, 1.29.6, 1.30.4. Upgrade to this version or later.
- Is CVE-2026-5724 exploitable, and should I be worried? Whether CVE-2026-5724 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-5724 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-5724?
- Upgrade
go.temporal.io/serverto 1.28.4 or later - Upgrade
go.temporal.io/serverto 1.29.6 or later - Upgrade
go.temporal.io/serverto 1.30.4 or later
- Upgrade