CVE-2026-65651

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” 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.7% (52nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-83892 (ENISA EUVD) · GHSA-7vcf-7m3r-v7x3 (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.7Exploit: None knownExposed services: Not assessed

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."

temporalio/sqlparser accepts SQL containing deeply nested unary expressions and can return a correspondingly deep abstract syntax tree without enforcing an applicable nesting limit. The library's String and Walk operations recursively traverse that tree. An application that parses attacker-controlled SQL and later formats or walks the returned tree can encounter a runtime-fatal Go stack overflow that terminates the process; Go panic recovery cannot contain this condition. Temporal Server passes caller-controlled query input through the affected parser in archival, visibility, and worker-query paths. In affected validation paths, the Server recursively formats an invalid expression while constructing an error. In a supported authenticated deployment, a caller with namespace read permission can terminate the receiving Frontend or Matching process. The dynamically confirmed ListWorkers route additionally requires at least one retained worker heartbeat. 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
39
EG Risk 39/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.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.7%
EPSS %ILE
52nd
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.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 (9)

Auto-updated Sep 21, 2026
Patch available. Sources: github_pr, github_release, github_commit.
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
Web page

temporal/common/archiver/filestore/queryParser.go at v0.10.0 · temporalio/temporal · GitHub

https://github.com/temporalio/temporal/blob/v0.10.0/common/archiver/filestore/queryParser.go#L77-L132
GitHub pull request

Update sqlparser dependency

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

https://github.com/temporalio/temporal/pull/11202
GitHub pull request Patch Available

Limit AST depth

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

https://github.com/temporalio/sqlparser/pull/7
Web page

GitHub - temporalio/sqlparser at v0.1.0 · GitHub

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

commit 0466b6b405ac (temporalio/sqlparser)

Patch available: temporalio/sqlparser v0.1.0 (contains commit 0466b6b405ac)

https://github.com/temporalio/sqlparser/commit/0466b6b405accfaa781e4bef417933efc18bcaef
GitHub pull request Patch Available

Limit depth of nested expressions

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

https://github.com/temporalio/sqlparser/pull/6
GitHub commit Patch Available

commit 1aae9baceee8 (temporalio/sqlparser)

Patch available: temporalio/sqlparser v0.1.0 (contains commit 1aae9baceee8)

https://github.com/temporalio/sqlparser/commit/1aae9baceee8e48525da8f56b07bf6a5ca7eb147

Vendor Advisories for CVE-2026-65651(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 / 67× 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 116 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 16 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-28 05:58 UTCEG score recompute
  7. 2026-10-28 05:58 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-25 14:11 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-10-20 18:41 UTCEG score recompute
  17. 2026-10-20 18:41 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  21. 2026-10-18 03:21 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 75 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-10-13 11:11 UTCEG score recompute
  3. 2026-10-13 11:11 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  5. 2026-10-12 15:46 UTCEG score recompute
  6. 2026-10-11 19:31 UTCEG score recompute
  7. 2026-10-11 18:32 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  8. 2026-10-11 16:47 UTCEG score recompute
  9. 2026-10-11 14:08 UTCEG score recompute
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-11 05:26 UTCEG score recompute
  12. 2026-10-11 05:26 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-10 17:35 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  15. 2026-10-10 05:43 UTCEG score recompute
  16. 2026-10-10 05:43 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-10-09 17:50 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  19. 2026-10-09 05:47 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  20. 2026-10-08 17:55 UTCEG score recompute
  21. 2026-10-08 17:55 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  22. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  23. 2026-10-08 05:46 UTCEG score recompute
  24. 2026-10-08 05:46 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  25. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  26. 2026-10-07 17:54 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  27. 2026-10-07 04:26 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  28. 2026-10-06 16:34 UTCEG score recompute
  29. 2026-10-06 16:34 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  30. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  31. 2026-10-06 04:39 UTCEG score recompute
  32. 2026-10-06 04:38 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  33. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  34. 2026-10-05 16:41 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  35. 2026-10-05 04:50 UTCEG score recompute
  36. 2026-10-05 04:50 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  37. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  38. 2026-10-04 16:58 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  39. 2026-10-04 05:06 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  40. 2026-10-03 17:15 UTCEG score recompute
  41. 2026-10-03 17:14 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  42. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  43. 2026-10-03 05:22 UTCEG score recompute
  44. 2026-10-03 05:22 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  45. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  46. 2026-10-02 17:31 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  47. 2026-10-02 05:40 UTCEG score recompute
  48. 2026-10-02 05:39 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  49. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  50. 2026-10-01 17:44 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  51. 2026-10-01 05:53 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  52. 2026-09-30 18:02 UTCEG score recompute
  53. 2026-09-30 18:02 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  54. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  55. 2026-09-30 06:11 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  56. 2026-09-29 18:19 UTCEG score recompute
  57. 2026-09-29 18:19 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  58. 2026-09-29 06:21 UTCEG score recompute
  59. 2026-09-29 06:21 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  60. 2026-09-28 18:30 UTCEG score recompute
  61. 2026-09-28 18:30 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  62. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  63. 2026-09-28 06:38 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  64. 2026-09-27 18:47 UTCEG score recompute
  65. 2026-09-27 18:47 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  66. 2026-09-27 06:55 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  67. 2026-09-26 19:03 UTCEG score recompute
  68. 2026-09-26 19:03 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  69. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  70. 2026-09-26 07:09 UTCEG score recompute
  71. 2026-09-26 07:08 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  72. 2026-09-25 19:17 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  73. 2026-09-25 07:11 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH
  74. 2026-09-24 19:20 UTCEG score recompute
  75. 2026-09-24 19:20 UTCGHSA enrichmentGHSA-7vcf-7m3r-v7x3 · GitHub severity HIGH

Frequently asked(5)

What is CVE-2026-65651?
CVE-2026-65651 is a high-severity vulnerability; its CVE record was published on September 21, 2026. temporalio/sqlparser accepts SQL containing deeply nested unary expressions and can return a correspondingly deep abstract syntax tree without enforcing an applicable nesting limit. The library's String and Walk operations recursively traverse that tree. An application that parses…
When was the CVE record for CVE-2026-65651 published?
The CVE record for CVE-2026-65651 was published on September 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 22, 2026; the record at its source may have been updated since.
Is CVE-2026-65651 actively exploited?
CVE-2026-65651 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65651?
CVE-2026-65651 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-65651?
A fix for CVE-2026-65651 is available: update to the fixed version the vendor names in its advisory. 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." The vendor advisories EchelonGraph has for CVE-2026-65651 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-65651?

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