CVE-2026-53554

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. 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
Elevated
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SQLBot is an intelligent Text-to-SQL system based on large language models and RAG. Prior to 1.9.0, the POST /api/v1/datasource/parseExcel endpoint in backend/apps/datasource/api/datasource.py uses attacker-controlled multipart filename data when selecting where uploaded content is stored, writes the content before spreadsheet parsing and validation finish, and can transform a double-extension filename into a Python source file. An attacker able to submit a crafted multipart upload can use these behaviors to place attacker-controlled content in /opt/sqlbot/app/alembic/versions/ even when a spreadsheet parsing failure after the file write causes the endpoint to return an error. The planted file remains on disk, and subsequent SQLBot startup or migration processing causes Alembic to import the module and execute its module-level statements in the SQLBot application runtime. This issue is fixed in version 1.9.0.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
49(Track*)
EG Risk 49/100SSVC: Track*

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
Severity73% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 23, 2026

Advisory Details (4)

Auto-updated Sep 17, 2026
🔬 Proof of concept available. 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 92c5aea70b2e (dataease/SQLBot)

Patch available: dataease/SQLBot v1.9.0 (contains commit 92c5aea70b2e)

https://github.com/dataease/SQLBot/commit/92c5aea70b2eba9c1f429017639017041556843b
github_commit Patch Available

commit 4bfd0f49e8cd (dataease/SQLBot)

Patch available: dataease/SQLBot v1.9.0 (contains commit 4bfd0f49e8cd)

https://github.com/dataease/SQLBot/commit/4bfd0f49e8cd3df8540dd9d51d40d0e056eeeec4
github Patch Available🟡 PoC Available

Arbitrary File Write via parseExcel Leading to Code Execution Through Alembic Import Processing · Advisory · dataease/SQLBot · GitHub

Affected: v1.9.0.

https://github.com/dataease/SQLBot/security/advisories/GHSA-wxv4-pw5w-wx79

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 16× 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-09-24 15:04 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-24 04:11 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 15:53 UTCEG score recompute
  6. 2026-09-22 05:02 UTCEG score recompute
  7. 2026-09-20 20:32 UTCEG score recompute
  8. 2026-09-20 20:16 UTCEPSS rescore
  9. 2026-09-19 22:52 UTCEG score recompute
  10. 2026-09-19 01:11 UTCEG score recompute
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-18 14:21 UTCEG score recompute
  13. 2026-09-18 13:29 UTCEG score recompute
  14. 2026-09-17 22:24 UTCEG score recompute
  15. 2026-09-17 21:44 UTCEG score recompute
  16. 2026-09-17 21:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53554?
CVE-2026-53554 is a high vulnerability 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, the POST /api/v1/datasource/parseExcel endpoint in backend/apps/datasource/api/datasource.py uses attacker-controlled multipart filename data when selecting where uploaded content is stored, writes…
When was CVE-2026-53554 disclosed?
CVE-2026-53554 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53554 actively exploited?
CVE-2026-53554 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53554?
CVE-2026-53554 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-53554?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53554, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53554?

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

Book a Demo →Browse All CVEs