CVE-2026-16651

High

Description

temporalio/sqlparser can panic when Parse, ParseStrictDDL, or ParseNext processes a MySQL version comment whose contents are empty or consist only of one to five decimal digits. ExtractMysqlComment does not check the -1 result returned by strings.IndexFunc before using it as a slice boundary. The resulting Go runtime panic propagates unless the caller recovers it on the parsing goroutine, so applications that parse attacker-controlled SQL can terminate. Temporal Server exposes the affected parser through ListWorkers. When that API is enabled, an authenticated caller with namespace read permission can submit a malformed query that terminates the receiving Matching process. Repeated requests can sustain a denial of service. The issue affects availability only; no confidentiality or integrity impact was identified.

SeverityHigh
CVSS8.7
Exploit probability—
ProductTemporal Technologies, Inc. Temporalio/sqlparser
PublishedSep 21, 2026
First seenSep 21, 2026
Weakness typeCWE-129CWE-129

How to fix

Affected products

ProductAffected versionsFixed in
Temporal Technologies, Inc. temporalio/sqlparser0.0.0-20180604150908-b055e9c9b4fa ≤ v < 0.0.0-20260721183040-74181ffcbaaf0.0.0-20260721183040-74181ffcbaaf
temporal temporal1.29.0 ≤ v ≤ 1.29.7, 1.30.0 ≤ v < 1.30.7, 1.31.0 ≤ v < 1.31.31.30.7, 1.31.3

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.