CVE-2026-65652

8.7

Temporal Technologies · tchannel-go

An improper array index validation in Temporal tchannel-go allows unauthenticated remote attackers to cause a process-terminating panic, resulting in a denial of service.

Executive summary

An unauthenticated remote denial of service vulnerability in Temporal tchannel-go allows attackers to crash hosting processes via malformed network frames.

Vulnerability

The software fails to validate the checksum-type field in incoming TChannel frames, leading to an out-of-bounds array index access that triggers an unrecovered Go panic. This vulnerability is exploitable by any unauthenticated network peer capable of reaching the listener.

Business impact

Successful exploitation of this vulnerability results in the immediate termination of the hosting process, causing a denial of service for applications relying on the affected library. With a CVSS score of 8.7, this flaw poses a significant availability risk to infrastructure components. Organizations may face service outages and operational disruption if the affected services are targeted by attackers.

Remediation

Immediate Action: Upgrade the tchannel-go dependency to version 1.22.1 or later to implement proper input validation.

Proactive Monitoring: Monitor application logs for frequent service restarts or unexpected Go panic stack traces indicating potential exploitation attempts.

Compensating Controls: Restrict network access to the TChannel listener to trusted peers using firewall rules or network segmentation to prevent unauthorized connections from untrusted sources.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the high severity of this denial of service vulnerability and its potential for automated exploitation, immediate patching is required. Organizations should identify all applications utilizing the tchannel-go library and prioritize updating the dependency to version 1.22.1 or later to eliminate the risk of 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.