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.
CVSS
No CVSS.
References
Configurations
No configuration.
History
21 Sep 2026, 12:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-21 12:17
Updated : 2026-09-22 19:40
NVD link : CVE-2026-16651
Mitre link : CVE-2026-16651
CVE.ORG link : CVE-2026-16651
JSON object : View
Products Affected
No product.
CWE
CWE-129
Improper Validation of Array Index
