CVE-2026-16651

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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.4%
EPSS %ILE
30th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 21, 2026

Last Modified

September 22, 2026

Advisory Details (7)

Auto-updated Sep 21, 2026
Patch available. Sources: github_pr, github_commit, github_release.
github_release Patch Available

v1.31.3

Patch available: temporalio/temporal v1.31.3

https://github.com/temporalio/temporal/releases/tag/v1.31.3
github_release Patch Available

v1.30.7

Patch available: temporalio/temporal v1.30.7

https://github.com/temporalio/temporal/releases/tag/v1.30.7
github_pr

Add 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/11090
github_pr

Update sqlparser dependency

Fix merged in temporalio/temporal PR #11190 on 2026-07-21 — awaiting tagged release

https://github.com/temporalio/temporal/pull/11190
generic

GitHub - temporalio/sqlparser at v0.1.0 · GitHub

https://github.com/temporalio/sqlparser/tree/v0.1.0
github_commit Patch Available

commit 74181ffcbaaf (temporalio/sqlparser)

Patch available: temporalio/sqlparser v0.1.0 (contains commit 74181ffcbaaf)

https://github.com/temporalio/sqlparser/commit/74181ffcbaaf0c52faa925f4cf27ed6c0c2be86f
github_pr Patch Available

Remove parsing MySQL special comments

Patch available: temporalio/sqlparser v0.1.0 (PR #5 merged 2026-07-21)

https://github.com/temporalio/sqlparser/pull/5

Vendor 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 28× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-04 03:49 UTCGHSA enrichment
  2. 2026-10-03 16:05 UTCEG score recompute
  3. 2026-10-03 16:04 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 04:20 UTCGHSA enrichment
  6. 2026-10-02 16:35 UTCEG score recompute
  7. 2026-10-02 16:35 UTCGHSA enrichment
  8. 2026-10-02 04:48 UTCEG score recompute
  9. 2026-10-02 04:48 UTCGHSA enrichment
  10. 2026-10-01 19:49 UTCEPSS rescore
  11. 2026-10-01 17:03 UTCGHSA enrichment
  12. 2026-10-01 04:57 UTCGHSA enrichment
  13. 2026-09-30 16:49 UTCEG score recompute
  14. 2026-09-30 16:49 UTCGHSA enrichment
  15. 2026-09-30 15:02 UTCEPSS rescore
  16. 2026-09-30 04:41 UTCGHSA enrichment
  17. 2026-09-29 16:48 UTCEG score recompute
  18. 2026-09-29 16:48 UTCGHSA enrichment
  19. 2026-09-29 15:20 UTCEPSS rescore
  20. 2026-09-29 04:49 UTCEG score recompute
  21. 2026-09-29 04:49 UTCGHSA enrichment
  22. 2026-09-28 17:04 UTCEG score recompute
  23. 2026-09-28 17:04 UTCGHSA enrichment
  24. 2026-09-28 13:51 UTCEPSS rescore
  25. 2026-09-28 05:11 UTCGHSA enrichment
Show 28 more
  1. 2026-09-27 17:27 UTCEG score recompute
  2. 2026-09-27 17:27 UTCGHSA enrichment
  3. 2026-09-27 13:47 UTCEPSS rescore
  4. 2026-09-27 05:42 UTCGHSA enrichment
  5. 2026-09-26 17:57 UTCEG score recompute
  6. 2026-09-26 17:57 UTCGHSA enrichment
  7. 2026-09-26 15:58 UTCEPSS rescore
  8. 2026-09-26 06:11 UTCEG score recompute
  9. 2026-09-26 06:11 UTCGHSA enrichment
  10. 2026-09-25 18:23 UTCGHSA enrichment
  11. 2026-09-25 06:38 UTCGHSA enrichment
  12. 2026-09-24 18:53 UTCEG score recompute
  13. 2026-09-24 18:53 UTCGHSA enrichment
  14. 2026-09-24 07:08 UTCGHSA enrichment
  15. 2026-09-23 19:23 UTCEG score recompute
  16. 2026-09-23 19:23 UTCGHSA enrichment
  17. 2026-09-23 07:38 UTCGHSA enrichment
  18. 2026-09-22 19:53 UTCGHSA enrichment
  19. 2026-09-22 15:56 UTCEG score recompute
  20. 2026-09-22 15:56 UTCGHSA enrichment
  21. 2026-09-22 04:10 UTCGHSA enrichment
  22. 2026-09-21 16:25 UTCEG score recompute
  23. 2026-09-21 16:25 UTCGHSA enrichment
  24. 2026-09-21 15:36 UTCEG score recompute
  25. 2026-09-21 15:35 UTCGHSA enrichment
  26. 2026-09-21 12:30 UTCEG score recompute
  27. 2026-09-21 11:45 UTCEG score recompute
  28. 2026-09-21 11:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16651?
CVE-2026-16651 is a high vulnerability published on September 21, 2026. 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…
When was CVE-2026-16651 disclosed?
CVE-2026-16651 was first published on September 21, 2026, with the most recent update on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16651 actively exploited?
CVE-2026-16651 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16651?
CVE-2026-16651 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16651?
A fix for CVE-2026-16651 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-16651 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16651

Explore →

Is Your Infrastructure Affected by CVE-2026-16651?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs