CVE-2026-65653

8.7

Temporal Technologies · tchannel-go

A failure to validate TChannel call fragments allows unauthenticated remote attackers to trigger a process crash via a malformed request, leading to a denial of service.

Executive summary

An unauthenticated remote denial of service vulnerability in Temporal tchannel-go allows attackers to terminate applications by sending malformed network packets.

Vulnerability

This vulnerability (CWE-129) occurs because the library fails to reject TChannel call fragments that lack length-prefixed argument chunks, leading to an out-of-bounds index access and a subsequent Go process panic. The flaw is exploitable by any unauthenticated remote peer capable of establishing a connection to the listener.

Business impact

The ability for an unauthenticated attacker to remotely crash a service poses a significant risk to business continuity. Given the CVSS score of 8.7, this is classified as a high-severity issue, as it permits the disruption of critical infrastructure without requiring prior access or interaction. Successful exploitation would result in service downtime and potential cascading failures in distributed systems relying on this library.

Remediation

Immediate Action: Update the dependency to version 1.22.1 or later to ensure the library properly validates TChannel fragments before processing.

Proactive Monitoring: Monitor service logs for unexpected process terminations or frequent service restarts that may indicate exploitation attempts.

Compensating Controls: Implement network-level access controls or firewalls to restrict inbound traffic to the affected service to known, trusted peers only.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

This vulnerability represents a critical availability risk for any application utilizing tchannel-go. Given the high CVSS score and the ease of exploitation, security teams should prioritize updating this library across all production environments immediately to prevent potential service disruption.

More Temporal Technologies CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by An external security researcher who reported this issue responsibly to Temporal Technologies, per the CVE Program record.