---
id: CVE-2026-5724
title: >-
  The frontend gRPC server's streaming interceptor chain did not include the
  authorization interceptor
summary: "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/S…"
severity: none
cwe:
  - CWE-306
published: '2026-04-10'
updated: '2026-07-08'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-5724'
references:
  - url: 'https://github.com/temporalio/temporal/releases/tag/v1.28.4'
    label: security@temporal.io
  - url: 'https://github.com/temporalio/temporal/releases/tag/v1.29.6'
    label: security@temporal.io
  - url: 'https://github.com/temporalio/temporal/releases/tag/v1.30.4'
    label: security@temporal.io
  - url: 'https://github.com/temporalio/temporal/releases/tag/v1.31.2'
    label: security@temporal.io
tags:
  - nvd
  - exploit-available
epss: 0.00665
epssPercentile: 0.49574
ingestedAt: '2026-07-08T20:46:41.561Z'
exploits:
  github: 1
  githubRepos:
    - 'https://github.com/tibrn/CVE-2026-5724'
  checkedAt: '2026-09-25T08:21:04.406Z'
exploitAvailable: true
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.