CVE-2026-65653

published 21 Sep 2026 · updated 21 Sep 2026

temporalio/tchannel-go zero-chunk call fragment causes process termination

8.7HighCVSS 8.7EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.22.1-0.20260720194454-0cb017f6870a.

github.com/temporalio/tchannel-go did not reject TChannel call fragments containing checksum metadata but no length-prefixed argument chunks. The fragment reader left its chunk slice empty and then unconditionally selected the first element. A network peer can supply such a malformed call fragment, including as a direct initial call request after completing the standard initialization handshake. On that inbound path, the resulting unrecovered Go slice-bounds panic occurs on a library-created dispatch goroutine and terminates the hosting process. This allows remote denial of service against applications that expose the listener to untrusted peers. The impact is limited to availability; no confidentiality or integrity impact was identified.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Temporal Technologies>=0.0.0-20150531204735-8d8ca17342b3 <1.22.1-0.20260720194454-0cb017f6870a1.22.1-0.20260720194454-0cb017f6870a

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-65653 severity on Zeptric[![CVE-2026-65653](https://zeptric.io/badge/cve/CVE-2026-65653.svg)](https://zeptric.io/cve/CVE-2026-65653)