Quick answers
- Is CVE-2026-16651 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16651 being exploited in the wild.
- How severe is CVE-2026-16651?
- Informational severity, published 21 September 2026.
- Which products and versions are affected?
- Temporal Technologies sqlparser; Temporal Technologies Temporal Server.
- Is there a fix for CVE-2026-16651?
- A patch was published on 2026-07-21. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-16651 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16651?
- Check whether you run Temporal Technologies Sqlparser or Temporal Technologies Temporal Server. 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 ExtractMysqlComment function in temporalio/sqlparser does not validate the return value of strings.IndexFunc before using it as a slice boundary, causing a panic when processing MySQL version comments that are empty or contain only 1-5 decimal digits. The vulnerability affects Parse, ParseStrictDDL, and ParseNext functions and requires an attacker to submit malformed SQL queries; Temporal Server exposes this through the ListWorkers API to authenticated callers.
Affected products
- Temporal Technologies sqlparser
- Temporal Technologies Temporal Server
Timeline
- 2026-09-21: disclosed
- 2026-07-21: patched