Is CVE-2026-5724 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-5724 being exploited in the wild.

How severe is CVE-2026-5724?

Medium severity, with a CVSS score of 4, published 10 April 2026.

Which products and versions are affected?

go.temporal.io/server (Go) SEMVER:introduced=0,fixed=1.28.4, SEMVER:introduced=0,fixed=1.28.4,introduced=1.29.0-135.0,fixed=1.29.6,introduced=1.30.0-143.0,fixed=1.30.4.

Is there a fix for CVE-2026-5724?

Yes. go.temporal.io/server (Go): upgrade to 1.28.4, 1.30.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-5724 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-5724?

Check whether you run go.temporal.io/server (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-5724: Temporal Server missing authentication in gRPC streaming interceptor

CVE-2026-5724 · Severity: medium · CVSS 4 · Published 2026-04-10

Temporal Server, a platform for managing durable business workflows, contains a security flaw where certain data replication requests do not require authentication. An attacker with network access to the server could potentially access sensitive workflow replication data without providing credentials. While exploiting this requires specific knowledge of the cluster's configuration, it could lead to unauthorized data exposure.

Technologies: go.temporal.io/server (Go). Vendors: Go.

Quick answers

Is CVE-2026-5724 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-5724 being exploited in the wild.
How severe is CVE-2026-5724?: Medium severity, with a CVSS score of 4, published 10 April 2026.
Which products and versions are affected?: go.temporal.io/server (Go) SEMVER:introduced=0,fixed=1.28.4, SEMVER:introduced=0,fixed=1.28.4,introduced=1.29.0-135.0,fixed=1.29.6,introduced=1.30.0-143.0,fixed=1.30.4.
Is there a fix for CVE-2026-5724?: Yes. go.temporal.io/server (Go): upgrade to 1.28.4, 1.30.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-5724 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-5724?: Check whether you run go.temporal.io/server (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

go.temporal.io/server (Go): upgrade to 1.28.4, 1.30.4 or later
```
go get go.temporal.io/server@v1.30.4
```

Technical details

The frontend gRPC server's streaming interceptor chain in Temporal Server was missing the authorization interceptor for specific endpoints. While unary RPCs correctly enforced authentication via ClaimMapper and Authorizer, the 'AdminService/StreamWorkflowReplicationMessages' endpoint remained accessible without credentials. This endpoint is hosted on the same port as the WorkflowService and cannot be disabled independently. An attacker with network access can initiate a replication stream; however, successful data exfiltration requires knowledge of the cluster ID and peer membership, as the history service performs secondary validation. Patches are available in versions 1.28.4, 1.29.6, 1.30.4, 1.31.2, and 1.32.0.

Affected products

Temporal Technologies, Inc. Temporal Server 1.24.0 to 1.28.3, 1.29.0 to 1.29.5, 1.30.0 to 1.30.3, 1.31.0 to 1.31.1

Identifiers

CVE-2026-5724
GHSA-q98v-9f9w-f49q
GO-2026-5578

Timeline

2026-04-10: disclosed
2026-04-10: patched: Initial patches released for 1.28, 1.29, and 1.30 lines.
2026-07-08: patched: Patch released for 1.31 line (v1.31.2).

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.