CVE-2026-61852 Chartbrew: SQL Injection via row_limit Parameter in AI runQuery Tool
Authenticated users can inject SQL via the AI runQuery tool's row_limit parameter to read or modify database data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-61852?
CVE-2026-61852 is a medium-severity SQL injection vulnerability in chartbrew, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.2, Chartbrew's runQuery() implementation in server/modules/ai/orchestrator/tools/runQuery.js interpolates the AI tool's row_limit parameter into a SQL LIMIT clause without runtime integer validation. The read-only keyword check runs before this value is appended, so an authenticated user who can influence a model-generated non-integer row_limit can add SQL that bypasses the earlier check. Successful exploitation can execute arbitrary statements against the connected database, including reading or changing data and, where database permissions permit, accessing files or executing operating-system commands. This issue is fixed in version 5.2.2.
Weakness: CWE-89
Which versions are affected by CVE-2026-61852?
How do I fix CVE-2026-61852?
No fix has been published for CVE-2026-61852 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-61852 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61852 exists.
Sources
Also known as GHSA-4923-m569-jc42.