Temporal Server contains an authorization flaw in the frontend gRPC server: the streaming interceptor chain did not include the authorization interceptor. As a result, when ClaimMapper and Authorizer are configured, unary RPCs correctly enforce authentication and authorization, but the streaming AdminService/StreamWorkflowReplicationMessages endpoint does not. This endpoint is exposed on the same frontend port as WorkflowService and cannot be disabled independently. An attacker with network access to the frontend gRPC port can open the replication stream without providing credentials. The history service still validates cluster IDs and peer membership before returning replication data, so exploitation for data access depends on a correctly configured replication target and attacker knowledge of the cluster configuration. Temporal Cloud is not affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.