CVE-2026-16651
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 32% of all known CVEs.
References
Related Vulnerabilities
Other CWE-129 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2021-35592 | Medium | 6.3 | 52% | - | Fix |
| CVE-2021-35598 | Medium | 6.3 | 51% | - | Fix |
| CVE-2021-35594 | Medium | 6.3 | 51% | - | Fix |
| CVE-2022-35737 | High | 7.5 | 24% | - | Fix |
| CVE-2014-6317 | High | 7.1 | 18% | - | - |
| CVE-2023-0755 | Critical | 9.8 | 12% | - | - |
Common questions
How do I fix CVE-2026-16651?
No published fix for CVE-2026-16651 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-16651 being actively exploited?
Not that we know of. CVE-2026-16651 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.39% is the estimated probability that it will be exploited in the next 30 days. That is higher than 32% of all scored CVEs.
How severe is CVE-2026-16651?
CVE-2026-16651 has a CVSS v4 base score of 8.7, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-16651
Markdown
[](https://tridentstack.com/cve/CVE-2026-16651)HTML
<a href="https://tridentstack.com/cve/CVE-2026-16651"><img src="https://tridentstack.com/cve/badge/CVE-2026-16651.svg" alt="CVE-2026-16651"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-22.