Which versions of SQLBot are affected by CVE-2026-42463?

SQLBot (DataEase) versions prior to 1.8.0 contain a critical data isolation flaw allowing authenticated users to access and modify database assets and configurations belonging to other business units…. A patch is available.

How to fix or mitigate CVE-2026-42463?

Within 24 hours: Identify all DataEase/SQLBot deployments and determine if any are running versions prior to 1.8.0; initiate emergency change control process. Within 7 days: Upgrade all affected instances to DataEase/SQLBot version 1.8.0 or later and validate multi-tenant isolation post-deployment. Within 30 days: Audit access logs for unauthorized cross-tenant access; document findings and completion of remediation.

SQLBot CVE-2026-42463

Q: What is the CVSS score of CVE-2026-42463?

CVE-2026-42463 has a CVSS 4.0 base score of 8.6 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-30182 HIGH

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-05-13 GitHub_M

Authentication Bypass Dataease Sqlbot

8.6

CVSS 4.0 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.6 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jun 08, 2026 - 09:07 vuln.today

Patch available

May 13, 2026 - 23:17 EUVD

CVSS changed

May 13, 2026 - 22:22 NVD

8.6 (HIGH)

CVE Published

May 13, 2026 - 21:26 nvd

UNKNOWN (no severity yet)

DescriptionGitHub Advisory

SQLBot is an intelligent Text-to-SQL system based on large language models and RAG. Prior to 1.8.0, SQLBot contains a Cross-Workspace IDOR (Insecure Direct Object Reference) and Authorization Bypass vulnerability in the /api/v1/datasource/exportDsSchema and /api/v1/datasource/uploadDsSchema endpoints. An attacker can access and modify database schemas and data sources belonging to other tenants/workspaces. This vulnerability is fixed in 1.8.0.

AnalysisAI

Cross-workspace IDOR in SQLBot (DataEase) versions prior to 1.8.0 allows authenticated low-privilege users to read and modify database schemas and data sources belonging to other tenants via the /api/v1/datasource/exportDsSchema and /api/v1/datasource/uploadDsSchema endpoints. The flaw breaks multi-tenant isolation in a Text-to-SQL platform that brokers access to backend databases, meaning a tenant can pivot to another tenant's data sources. No public exploit identified at time of analysis, and EPSS probability is very low (0.04%), but SSVC rates technical impact as total.

Technical ContextAI

SQLBot is a DataEase-maintained Text-to-SQL system that uses large language models and retrieval-augmented generation (RAG) to translate natural-language questions into SQL against registered data sources, with workspace/tenant boundaries used to segregate customers. The vulnerability is a CWE-639 (Authorization Bypass Through User-Controlled Key) flaw in the datasource schema export and upload endpoints: the application trusts a client-supplied data source or workspace identifier without verifying that the authenticated principal owns the referenced workspace. Because these endpoints govern the schema definitions that the LLM/RAG pipeline uses to reason about backend databases, breaking the object-level authorization check exposes the configuration of every tenant's data sources. The affected CPE is cpe:2.3:a:dataease:sqlbot:*:*:*:*:*:*:*:* up to and not including 1.8.0.

RemediationAI

Upgrade SQLBot to version 1.8.0 or later, which contains the vendor-released patch per the GHSA-pq2r-fj48-xfpp advisory (https://github.com/dataease/SQLBot/security/advisories/GHSA-pq2r-fj48-xfpp). Until upgrade is possible, restrict network access to the /api/v1/datasource/exportDsSchema and /api/v1/datasource/uploadDsSchema endpoints at a reverse proxy or WAF - for example, block these two paths for all non-administrative principals - accepting that this will break legitimate schema export/import workflows for end users. In multi-tenant deployments, audit application and database logs for cross-workspace identifiers appearing in requests made by tenants that should not own them, and review existing data source definitions and schemas for unauthorized modifications, since the integrity impact means tampering may have already occurred. Avoid relying solely on UI-level role restrictions because the bypass is at the API authorization layer.