CVE-2026-53557

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (27th 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

Also known asEUVD-2026-82564 (ENISA EUVD)Source: ENISA EUVD

7.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.3%CVSS: 7.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

SQLBot is an intelligent Text-to-SQL system based on large language models and RAG. Prior to 1.9.0, an authenticated user can supply a crafted sheet["tableName"] value in the Excel datasource configuration submitted through POST /api/v1/datasource/, and SQLBot stores that value without safe identifier handling. When the same datasource is later removed through DELETE /api/v1/datasource/{id}, the stored value is interpolated into datasource cleanup SQL and executed by PostgreSQL. This second-order SQL injection can invoke PostgreSQL COPY TO PROGRAM and execute arbitrary operating-system commands with the privileges of the postgres process inside the SQLBot container. This issue is fixed in version 1.9.0.

CVSS
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.3%
EPSS %ILE
27th
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 (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; 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 total (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 17, 2026

Last Modified

September 23, 2026

Advisory Details (3)

Auto-updated Sep 17, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v1.9.0

Patch available: dataease/SQLBot v1.9.0

https://github.com/dataease/SQLBot/releases/tag/v1.9.0
GitHub commit Patch Available

commit 5d5a92a5266e (dataease/SQLBot)

Patch available: dataease/SQLBot v1.9.0 (contains commit 5d5a92a5266e)

https://github.com/dataease/SQLBot/commit/5d5a92a5266e62da7de4a84ffc8317498497b193
GitHub advisoryMentions a patch (unverified)

Second-Order SQL Injection via Excel Datasource Leading to Remote Command Execution · Advisory · dataease/SQLBot · GitHub

Affected: v1.9.0.

https://github.com/dataease/SQLBot/security/advisories/GHSA-vxwj-843f-9c9g

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  4. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  6. 2026-11-08 05:33 UTCEchelonGraph re-scored
  7. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  8. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  11. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  12. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  13. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  14. 2026-10-31 22:33 UTCEchelonGraph re-scored
  15. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  16. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  17. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  18. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  19. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  20. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  21. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  22. 2026-10-25 14:20 UTCEchelonGraph re-scored
  23. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-10-24 15:34 UTCEchelonGraph re-scored
  25. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
Show 66 more
  1. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  3. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  5. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-18 03:31 UTCEchelonGraph re-scored
  7. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-17 08:36 UTCEchelonGraph re-scored
  9. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  10. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-12 15:57 UTCEchelonGraph re-scored
  15. 2026-10-11 19:40 UTCEchelonGraph re-scored
  16. 2026-10-11 16:55 UTCEchelonGraph re-scored
  17. 2026-10-11 14:19 UTCEchelonGraph re-scored
  18. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-10-11 03:40 UTCEchelonGraph re-scored
  20. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-10-10 05:44 UTCEchelonGraph re-scored
  22. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-10-08 20:25 UTCEchelonGraph re-scored
  24. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-10-08 08:16 UTCEchelonGraph re-scored
  26. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  27. 2026-10-06 23:26 UTCEchelonGraph re-scored
  28. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  29. 2026-10-06 01:34 UTCEchelonGraph re-scored
  30. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  31. 2026-10-05 03:39 UTCEchelonGraph re-scored
  32. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  33. 2026-10-03 18:52 UTCEchelonGraph re-scored
  34. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  35. 2026-10-02 20:41 UTCEchelonGraph re-scored
  36. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  37. 2026-10-01 22:49 UTCEchelonGraph re-scored
  38. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  39. 2026-10-01 00:55 UTCEchelonGraph re-scored
  40. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  41. 2026-09-29 16:09 UTCEchelonGraph re-scored
  42. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  43. 2026-09-29 05:12 UTCEchelonGraph re-scored
  44. 2026-09-28 18:17 UTCEchelonGraph re-scored
  45. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  46. 2026-09-27 19:49 UTCEchelonGraph re-scored
  47. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  48. 2026-09-26 21:57 UTCEchelonGraph re-scored
  49. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  50. 2026-09-26 11:02 UTCEchelonGraph re-scored
  51. 2026-09-24 15:11 UTCEchelonGraph re-scored
  52. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  53. 2026-09-24 04:16 UTCEchelonGraph re-scored
  54. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  55. 2026-09-23 00:21 UTCEchelonGraph re-scored
  56. 2026-09-22 02:29 UTCEchelonGraph re-scored
  57. 2026-09-22 02:02 UTCEchelonGraph re-scored
  58. 2026-09-22 01:07 UTCEchelonGraph re-scored
  59. 2026-09-21 03:17 UTCEchelonGraph re-scored
  60. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  61. 2026-09-19 18:28 UTCEchelonGraph re-scored
  62. 2026-09-18 20:37 UTCEchelonGraph re-scored
  63. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  64. 2026-09-17 22:24 UTCEchelonGraph re-scored
  65. 2026-09-17 21:50 UTCEchelonGraph re-scoredFirst assessed: 7.7 HIGH
  66. 2026-09-17 21:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53557?
CVE-2026-53557 is a high-severity vulnerability; its CVE record was published on September 17, 2026. SQLBot is an intelligent Text-to-SQL system based on large language models and RAG. Prior to 1.9.0, an authenticated user can supply a crafted sheet["tableName"] value in the Excel datasource configuration submitted through POST /api/v1/datasource/, and SQLBot stores that value without safe…
When was the CVE record for CVE-2026-53557 published?
The CVE record for CVE-2026-53557 was published on September 17, 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-53557 actively exploited?
CVE-2026-53557 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53557?
CVE-2026-53557 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53557?
A fix for CVE-2026-53557 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53557?

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