CVE-2026-65652

temporalio/tchannel-go malformed checksum type causes process termination

  • High 8.7

Description

github.com/temporalio/tchannel-go did not validate the one-byte checksum-type field in inbound TChannel call frames. A network peer that can reach a listener can complete the standard initialization handshake and send a call request with an unsupported checksum type. The parser uses that value as an index into a four-entry checksum pool, causing an unrecovered Go panic on the connection read goroutine and terminating 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.

Key facts

Published
21 Sep 2026
Last changed
21 Sep 2026
Assigned by
Temporal
EPSS
0.71% likely to be exploited in the next 30 days, higher than 54.082% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.7CVSS 4.0, Highfrom the CNA (Temporal)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

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Temporal Technologies, Inc.temporalio/tchannel-go
  • Default status: unaffected
  • 0.0.0-20160105034737-a6904155f628 up to but excluding 1.22.1-0.20260720194454-0cb017f6870a (affected)

Timeline

  1. 21 Sep 2026 Published

Weakness

References