CVE-2026-16651: temporalio/sqlparser malformed MySQL version comments can cause a panic
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
github.com/temporalio/sqlparserto a version that resolves this vulnerability.Fixed in v0.0.0-20260721183040-74181ffcbaaf - Upgrade
Upgrade
Temporal Serverto a version that resolves this vulnerability.Fixed in 1.30.7 - Upgrade
Upgrade
Temporal Serverto a version that resolves this vulnerability.Fixed in 1.31.3 - Upgrade
Upgrade
Temporal Serverto a version that resolves this vulnerability.Fixed in 1.32.0