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.
CVE-2026-16651
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-83891 (ENISA EUVD) · GHSA-g9jq-gq4v-4rw3 (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
Fixed versions, as the CVE record's CNA (Temporal Technologies Inc.) states them: "Temporal Server operators should upgrade to 1.30.7, 1.31.3, or 1.32.0, as appropriate for the deployed minor release line."
- CVSS v3
- 8.7
- EG Score
- 8.7HIGHmedium confidence
- EG Risk
- 54EG Risk 54/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity87% × 45%Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.5% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.5%
- EPSS %ILE
- 44th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 21, 2026
Last Modified
September 22, 2026
Advisory Details (7)
Auto-updated Sep 21, 2026v1.31.3
Patch available: temporalio/temporal v1.31.3
https://github.com/temporalio/temporal/releases/tag/v1.31.3v1.30.7
Patch available: temporalio/temporal v1.30.7
https://github.com/temporalio/temporal/releases/tag/v1.30.7Add panic handlers to matching handler APIs for consistency
Fix merged in temporalio/temporal PR #11090 on 2026-07-15 — awaiting tagged release
https://github.com/temporalio/temporal/pull/11090Update sqlparser dependency
Fix merged in temporalio/temporal PR #11190 on 2026-07-21 — awaiting tagged release
https://github.com/temporalio/temporal/pull/11190GitHub - temporalio/sqlparser at v0.1.0 · GitHub
https://github.com/temporalio/sqlparser/tree/v0.1.0commit 74181ffcbaaf (temporalio/sqlparser)
Patch available: temporalio/sqlparser v0.1.0 (contains commit 74181ffcbaaf)
https://github.com/temporalio/sqlparser/commit/74181ffcbaaf0c52faa925f4cf27ed6c0c2be86fRemove parsing MySQL special comments
Patch available: temporalio/sqlparser v0.1.0 (PR #5 merged 2026-07-21)
https://github.com/temporalio/sqlparser/pull/5Vendor Advisories for CVE-2026-16651(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 68× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 117 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 17 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-30 08:45 UTCEG score recompute
- 2026-10-30 08:45 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-25 14:46 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-24 01:24 UTCEG score recompute
- 2026-10-24 01:24 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-18 04:00 UTCEG score recompute
- 2026-10-17 18:02 UTCEG score recompute
- 2026-10-17 18:02 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Show 75 moreShow fewer
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-12 16:30 UTCEG score recompute
- 2026-10-12 04:47 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-11 20:09 UTCEG score recompute
- 2026-10-11 17:21 UTCEG score recompute
- 2026-10-11 16:04 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-11 14:54 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-11 04:19 UTCEG score recompute
- 2026-10-11 04:19 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-10 16:33 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-10 04:47 UTCEG score recompute
- 2026-10-10 04:47 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-09 16:52 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-09 05:05 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-08 17:19 UTCEG score recompute
- 2026-10-08 17:19 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-08 02:08 UTCEG score recompute
- 2026-10-08 02:08 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-07 14:23 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-07 02:38 UTCEG score recompute
- 2026-10-07 02:38 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-06 14:53 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-06 03:07 UTCEG score recompute
- 2026-10-06 03:07 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-05 15:22 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-05 03:19 UTCEG score recompute
- 2026-10-05 03:19 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-04 15:34 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-04 03:49 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-03 16:05 UTCEG score recompute
- 2026-10-03 16:04 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-03 04:20 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-02 16:35 UTCEG score recompute
- 2026-10-02 16:35 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-02 04:48 UTCEG score recompute
- 2026-10-02 04:48 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-01 17:03 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-10-01 04:57 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-30 16:49 UTCEG score recompute
- 2026-09-30 16:49 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-30 04:41 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-29 16:48 UTCEG score recompute
- 2026-09-29 16:48 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-29 04:49 UTCEG score recompute
- 2026-09-29 04:49 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-28 17:04 UTCEG score recompute
- 2026-09-28 17:04 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-28 05:11 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-27 17:27 UTCEG score recompute
- 2026-09-27 17:27 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-27 05:42 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-26 17:57 UTCEG score recompute
- 2026-09-26 17:57 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-26 06:11 UTCEG score recompute
- 2026-09-26 06:11 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-25 18:23 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
- 2026-09-25 06:38 UTCGHSA enrichmentGHSA-g9jq-gq4v-4rw3 · GitHub severity HIGH
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-16651?
When was the CVE record for CVE-2026-16651 published?
Is CVE-2026-16651 actively exploited?
What is the CVSS score of CVE-2026-16651?
How do I remediate CVE-2026-16651?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16651
Is Your Infrastructure Affected by CVE-2026-16651?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.