temporalio/sqlparser malformed MySQL version comments can cause a panic
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Temporal Technologies, Inc. | temporalio/sqlparser | unaffected |
|
||||||||||||
| Temporal Technologies, Inc. | Temporal Server | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Temporal | Sqlparser |
|
||||||||||||||||
| Temporal | Temporal |
|
Vendor Solution
Upgrade github.com/temporalio/sqlparser to v0.0.0-20260721183040-74181ffcbaaf or later. Temporal Server operators should upgrade to 1.30.7, 1.31.3, or 1.32.0, as appropriate for the deployed minor release line. The parser fix treats MySQL version comments as ordinary comments instead of interpreting their contents as SQL.
Vendor Workaround
Until upgrading, applications can reject MySQL version comments before invoking the parser or recover parser panics on the parsing goroutine. Temporal Server 1.29 and 1.30 operators can set frontend.ListWorkersEnabled to false. On any affected Server release, restrict ListWorkers to trusted principals or apply the matching-handler panic-recovery change as interim containment. Panic recovery does not replace the parser fix.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.532% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Temporal sqlparser
|
|
| Vendors & Products |
Temporal sqlparser
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | temporalio/sqlparser malformed MySQL version comments can cause a panic | |
| First Time appeared |
Temporal
Temporal temporal |
|
| Weaknesses | CWE-129 | |
| CPEs | cpe:2.3:a:temporal:temporal:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Temporal
Temporal temporal |
|
| References |
|
|
| Metrics |
cvssV4_0
|