CVE-2026-53556

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% 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
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.0Exploit: 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/previewData endpoint in backend/apps/datasource/crud/datasource.py incorporates the client-controlled table_name value into generated SQL without safe identifier handling. An authenticated user can configure a datasource for SQLBot's internal PostgreSQL service and submit a crafted table_name that remains a SELECT operation under the read-only policy while invoking pg_read_file(), pg_read_binary_file(), or pg_ls_dir(). In the default tested trusted loopback authentication configuration, the internal connection accepts invalid credentials and executes with PostgreSQL superuser privileges, allowing filesystem content such as /etc/hosts and /etc/passwd to be returned in the previewData API response and potentially exposing configuration, credentials, authentication secrets, and source code. This issue is fixed in version 1.9.0.

CVSS v3
6.0
EG Score
6.0(medium)
EG Risk
43(Track)
EG Risk 43/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
Severity60% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
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_pr, 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 76b5176b0e39 (dataease/SQLBot)

Patch available: dataease/SQLBot v1.9.0 (contains commit 76b5176b0e39)

https://github.com/dataease/SQLBot/commit/76b5176b0e394740fd07c0d1769c0c792e8cb3b4
github_pr Patch Available

fix: Fix SQL injection vulnerability

Patch available: dataease/SQLBot v1.9.0 (PR #1156 merged 2026-06-03)

https://github.com/dataease/SQLBot/pull/1156
github Patch Available🟡 PoC Available

Authenticated SQL Injection in previewData Resulting in Arbitrary File Read · Advisory · dataease/SQLBot · GitHub

Affected: v1.9.0.

https://github.com/dataease/SQLBot/security/advisories/GHSA-vwjq-5h4h-x8g5

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 14× 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 18:07 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 23:41 UTCEG score recompute
  5. 2026-09-21 22:54 UTCEG score recompute
  6. 2026-09-20 22:08 UTCEG score recompute
  7. 2026-09-20 20:16 UTCEPSS rescore
  8. 2026-09-19 21:21 UTCEG score recompute
  9. 2026-09-18 20:34 UTCEG score recompute
  10. 2026-09-18 20:10 UTCEG score recompute
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-17 22:24 UTCEG score recompute
  13. 2026-09-17 21:49 UTCEG score recompute
  14. 2026-09-17 21:49 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53556?
CVE-2026-53556 is a medium 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/previewData endpoint in backend/apps/datasource/crud/datasource.py incorporates the client-controlled tablename value into generated SQL without safe identifier handling.…
When was CVE-2026-53556 disclosed?
CVE-2026-53556 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-53556 actively exploited?
CVE-2026-53556 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 61.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53556?
CVE-2026-53556 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2026-53556?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53556, 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-53556

Explore →

Is Your Infrastructure Affected by CVE-2026-53556?

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

Book a Demo →Browse All CVEs