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.
{
"cna_assigner": "Temporal",
"cwe_ids": [
"CWE-129"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/16xxx/CVE-2026-16651.json",
"unresolved_ranges": [
{
"extracted_events": [
{
"introduced": "0.0.0-20180604150908-b055e9c9b4fa"
},
{
"fixed": "0.0.0-20260721183040-74181ffcbaaf"
}
],
"source": "AFFECTED_FIELD"
}
]
}{
"source": "REFERENCES"
}
{
"extracted_events": [
{
"introduced": "1.29.0"
},
{
"last_affected": "1.29.7"
},
{
"introduced": "1.30.0"
},
{
"fixed": "1.30.7"
},
{
"introduced": "1.31.0"
},
{
"fixed": "1.31.3"
}
],
"source": [
"AFFECTED_FIELD",
"REFERENCES"
]
}