Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-65653— temporalio/tchannel-go zero-chunk call fragment causes process termination

Quick assessment

Affected
Temporal Technologies, Inc. temporalio/tchannel-go
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

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

CVSS 8.7 · High EPSS 0.68% · P51

Affected Version Matrix 1

VendorProduct Version RangeStatus
Temporal Technologies, Inc. temporalio/tchannel-go 0.0.0-20150531204735-8d8ca17342b3< 1.22.1-0.20260720194454-0cb017f6870a affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-65653

Vulnerability Information

Shenlong is analyzing...

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
temporalio/tchannel-go zero-chunk call fragment causes process termination
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
对数组索引的验证不恰当
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Temporal Technologies, Inc. temporalio/tchannel-go 0.0.0-20150531204735-8d8ca17342b3 ~ 1.22.1-0.20260720194454-0cb017f6870a -

II. Public POCs for CVE-2026-65653

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-65653

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-65653 (3)

Other References for CVE-2026-65653 (2)

Same Patch Batch · Temporal Technologies, Inc. · 2026-09-21 · 8 CVEs total

CVE-2026-89139 8.7 HIGH Temporal Server worker deployment compute provider executes a caller-supplied command on t
CVE-2026-65654 8.7 HIGH temporalio/ringpop-go fails to enforce configured label limits on inbound membership gossi
CVE-2026-65652 8.7 HIGH temporalio/tchannel-go malformed checksum type causes process termination
CVE-2026-87858 7.2 HIGH Temporal Server completion callback source header can direct attacker-chosen requests to t
CVE-2026-16652 7.1 HIGH Temporal Server Schedule exclusion search can cause excessive CPU consumption
CVE-2026-16651 7.1 HIGH temporalio/sqlparser malformed MySQL version comments can cause a panic
CVE-2026-65651 6.0 MEDIUM temporalio/sqlparser deeply nested unary expressions can cause a fatal stack overflow duri

IV. Related Vulnerabilities

Same product: temporalio/tchannel-go
Same vendor: Temporal Technologies, Inc.
Same weakness: CWE-129

V. Comments for CVE-2026-65653

No comments yet

Leave a comment