Quick answers
- Is CVE-2026-65653 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65653 being exploited in the wild.
- How severe is CVE-2026-65653?
- Informational severity, published 21 September 2026.
- Which products and versions are affected?
- Temporal Tchannel-Go before fix.
- Is there a fix for CVE-2026-65653?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-65653 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-65653?
- Check whether you run Temporal Tchannel-Go at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The fragment reader in tchannel-go fails to validate that TChannel call fragments with checksum metadata contain at least one length-prefixed argument chunk. When such malformed fragments are received, the code attempts to access the first element of an empty chunk slice, triggering an unrecovered panic in a dispatch goroutine. This occurs on the inbound path after the TChannel handshake, allowing any network-accessible peer to trigger remote process termination.
Affected products
- Temporal tchannel-go before fix
Timeline
- 2026-09-21: disclosed