Skip to content

CVE-2026-16651 temporalio/sqlparser malformed MySQL version comments can cause a panic

HighCVSS 7.1 EPSS 0.53%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: yes · technical impact: partial
Technology
MySQL

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.

Upgrade path

2 packages: 2 fixed.

PackageAffectedFixed inStatus
temporal(Go) >= 1.29.0, <= 1.29.7; >= 1.30.0, < 1.30.7; >= 1.31.0, < 1.31.3 1.30.7, 1.31.3 Fixed
temporalio github.com/temporalio/sqlparser(Go) >= 0.0.0-20180604150908-b055e9c9b4fa, < 0.0.0-20260721183040-74181ffcbaaf 0.0.0-20260721183040-74181ffcbaaf Fixed

Affected products

ProductAffected versionsFixed in
temporalio github.com/temporalio/sqlparser(Go) >= 0.0.0-20180604150908-b055e9c9b4fa, < 0.0.0-20260721183040-74181ffcbaaf 0.0.0-20260721183040-74181ffcbaaf
temporal(Go) >= 1.29.0, <= 1.29.7 No fix listed
temporal(Go) >= 1.30.0, < 1.30.7 1.30.7
temporal(Go) >= 1.31.0, < 1.31.3 1.31.3

References