Temporal Technologies, Inc. temporalio/tchannel-go
temporalio/tchannel-go zero-chunk call fragment causes process termination
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.0.0-20150531204735-8d8ca17342b3, < 1.22.1-0.20260720194454-0cb017f6870a
Fixed in 1.22.1-0.20260720194454-0cb017f6870a
Mitigation
Upgrade github.com/temporalio/tchannel-go to v1.22.1 or later. The fix rejects fragments containing no argument chunks before indexing the chunk slice.
Workaround
Restrict TChannel listener access to trusted peers. Where supported by the embedding application, require mutually authenticated TLS so peers without a trusted client certificate are rejected before TChannel frame parsing. External panic-recovery middleware is not a reliable mitigation because the confirmed inbound panic occurs on a library-created dispatch goroutine.
References
- Patch github.com/temporalio/tchannel-go/commit/8d8ca…
- Patch github.com/temporalio/tchannel-go/commit/1dcfa…
- Patch github.com/temporalio/tchannel-go/pull/14
1 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.