dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-5724

MEDIUM · 6.3 CVSS v4.0 Published 2026-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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. The fix was applied per release line: it is present in 1.28.4, 1.29.6, 1.30.4, 1.31.2, and 1.32.0 and later releases on each line. Releases 1.31.0 and 1.31.1 do not contain the fix and are affected. Temporal Cloud is not affected.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The frontend gRPC server's streaming interceptor chain lacks the authorization interceptor, allowing unauthenticated access to the AdminService/StreamWorkflowReplicationMessages endpoint even when ClaimMapper and Authorizer are configured. This enables attackers with network access to open replication streams without credentials, potentially exfiltrating workflow history data, though exploitation requires a correctly configured replication target and knowledge of cluster configuration.

MitigationUpgrade to the patched versions (1.28.4+, 1.29.6+, 1.30.4+, 1.31.2+, 1.32.0+) which include the authorization interceptor in the streaming interceptor chain. If upgrading is not immediately possible, restrict network access to the frontend port and ensure replication targets are not exposed to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
None
User interaction
None
Scope
N

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:L/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:X/RE:L/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Temporal version
    Query the system or check the version file/configuration for the Temporal frontend service (e.g., via administrative API, container image tag, or deployment manifest)
    Affected if The installed version is earlier than 1.28.4, 1.29.6, 1.30.4, 1.31.2, or 1.32.0, or if the version cannot be determined but is known to be an unpatched release
  2. Determine if cross-cluster replication is configured
    Check the cluster configuration for active replication targets or namespace replication settings that enable the AdminService/StreamWorkflowReplicationMessages endpoint
    Affected if Replication targets are configured and active, as exploitation requires a correctly configured replication target
  3. Verify network exposure of the frontend gRPC port
    Inspect the network binding or firewall rules for the frontend gRPC service port to determine if it is accessible from untrusted networks
    Affected if The frontend port is bound to a non-localhost address or exposed to networks beyond the trusted cluster network
  4. Confirm authorization is configured
    Review the cluster configuration for ClaimMapper and Authorizer settings to verify that authentication/authorization is enabled
    Affected if ClaimMapper and Authorizer are configured (note: the vulnerability bypasses these even when properly set up)

A user is affected if their Temporal version is unpatched (prior to 1.28.4/1.29.6/1.30.4/1.31.2/1.32.0), cross-cluster replication is configured, and the frontend port is network-accessible, regardless of whether authorization is configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the patched versions (1.28.4+, 1.29.6+, 1.30.4+, 1.31.2+, 1.32.0+) which include the authorization interceptor in the streaming interceptor chain. If upgrading is not immediately possible, restrict network access to the frontend port and ensure replication targets are not exposed to untrusted networks.

Recommended fix High confidence

Upgrade to 1.28.4, 1.29.6, 1.30.4, 1.31.2, or 1.32.0 (or later) depending on your release line

  1. 1. Identify the currently deployed Temporal version by checking the server logs or deployment configuration.
  2. 2. Determine which release line (1.28, 1.29, 1.30, 1.31, or 1.32) your current version belongs to.
  3. 3. If running 1.28.x, upgrade to version 1.28.4 or later.
  4. 4. If running 1.29.x, upgrade to version 1.29.6 or later.
  5. 5. If running 1.30.x, upgrade to version 1.30.4 or later.
  6. 6. If running 1.31.0 or 1.31.1, upgrade to version 1.31.2 or later.
  7. 7. If running 1.32.x or later, the fix is already included.
  8. 8. After upgrade, verify that the AdminService/StreamWorkflowReplicationMessages endpoint now properly enforces authentication.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5724 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data