CVE-2026-61851: Chartbrew: Incomplete Read-Only Keyword Blocklist in AI runQuery Tool
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 attempts to enforce read-only database access with a blocklist containing only seven SQL keywords. An authenticated user with AI feature access can submit dangerous statements or database functions that are absent from the read-only keyword blocklist, causing them to execute without SQL injection or keyword-obfuscation techniques. Depending on the database engine, configuration, and database-user privileges, this can expose or write files, access internal network resources, change database privileges, execute commands, or alter data. This issue is fixed in version 5.2.2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Chartbrew (runQuery tool)to a version that resolves this vulnerability.Fixed in 5.2.2
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated user with access to Chartbrew's AI feature can exploit it. The impact depends on the connected database engine, its configuration, and the privileges assigned to the database user.
Does exploitation require SQL injection or bypassing the keyword filter through obfuscation?
No. An attacker can submit dangerous SQL statements or database functions that are not among the seven blocked keywords, without SQL injection or keyword-obfuscation techniques.
What could an attacker do through an affected deployment?
Depending on the database environment and database-user privileges, an attacker may expose or write files, access internal network resources, modify database privileges, execute commands, or alter data.
Which versions are affected and what version fixes the issue?
Chartbrew versions prior to 5.2.2 are affected. The issue is fixed in version 5.2.2.