Skip to main content

Sqlbot CVE-2026-32949

| EUVD-2026-13541 HIGH
External Control of File Name or Path (CWE-73)
2026-03-20 security-advisories@github.com
7.5
CVSS 3.1 · GitHub Advisory
Share

Severity by source

GitHub Advisory PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

6
Analysis Updated
Apr 16, 2026 - 06:20 EUVD-patch-fix
executive_summary
Re-analysis Queued
Apr 16, 2026 - 05:29 backfill_euvd_patch
patch_released
Patch available
Apr 16, 2026 - 05:29 EUVD
1.7.0
EUVD ID Assigned
Mar 20, 2026 - 08:37 euvd
EUVD-2026-13541
Analysis Generated
Mar 20, 2026 - 08:37 vuln.today
CVE Published
Mar 20, 2026 - 05:16 nvd
HIGH 7.5

DescriptionGitHub Advisory

SQLBot is an intelligent data query system based on a large language model and RAG. Versions prior to 1.7.0 contain a Server-Side Request Forgery (SSRF) vulnerability that allows an attacker to retrieve arbitrary system and application files from the server. An attacker can exploit the /api/v1/datasource/check endpoint by configuring a forged MySQL data source with a malicious parameter extraJdbc="local_infile=1". When the SQLBot backend attempts to verify the connectivity of this data source, an attacker-controlled Rogue MySQL server issues a malicious LOAD DATA LOCAL INFILE command during the MySQL handshake. This forces the target server to read arbitrary files from its local filesystem (such as /etc/passwd or configuration files) and transmit the contents back to the attacker. This issue was fixed in version 1.7.0.

AnalysisAI

A Server-Side Request Forgery (SSRF) vulnerability in SQLBot, an intelligent data query system based on large language models and RAG, allows unauthenticated remote attackers to read arbitrary files from the server's filesystem. SQLBot versions prior to 1.7.0 are affected, with the vulnerability exploitable through the /api/v1/datasource/check endpoint by configuring a malicious MySQL data source that triggers a LOAD DATA LOCAL INFILE attack during connection verification. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Craft malicious MySQL datasource with local_infile=1
Delivery
Submit to /api/v1/datasource/check endpoint
Exploit
SQLBot verifies connectivity to rogue MySQL server
Execution
Server issues LOAD DATA LOCAL INFILE
Impact
Arbitrary files retrieved from backend system

Vulnerability AssessmentAI

Exploitation SQLBot versions prior to 1.7.0. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 4.0 score of 8.7 reflects high severity with network attack vector (AV:N), low complexity (AC:L), no privileges required (PR:N), and high confidentiality impact (VC:H). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An unauthenticated attacker accesses the publicly exposed /api/v1/datasource/check endpoint and submits a crafted MySQL data source configuration containing extraJdbc parameter set to local_infile=1, along with connection details pointing to their malicious MySQL server. When SQLBot attempts to verify the data source connectivity, the attacker's rogue MySQL server responds with LOAD DATA LOCAL INFILE commands during the handshake, forcing SQLBot to read sensitive files like /etc/passwd, application configuration files containing database credentials, or cloud instance metadata, and transmit the contents back to the attacker for credential harvesting and lateral movement.
Remediation Upgrade SQLBot to version 1.7.0 or later, which contains the security fix as documented in the release notes at https://github.com/dataease/SQLBot/releases/tag/v1.7.0. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours: Identify all SQLBot instances in your environment and document current versions. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-32949 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy