CVE-2026-69128: Path Traversal
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. In 5.2.2, the AI SQL blocklist omitted sibling PostgreSQL filesystem functions and failed to match double-quoted identifier forms of denied functions. The vulnerable surface is the AI query tool's PostgreSQL SQL-validation blocklist. A team Owner or Admin uses an AI-enabled PostgreSQL connection whose database role can call server-side file functions and causes generated SQL to use an unlisted sibling function or a double-quoted denied function. Unlisted sibling functions remain allowed, and double-quoted function identifiers bypass the denylist regular expressions and reach PostgreSQL. AI features must be enabled and the user must have elevated Chartbrew privileges. A PostgreSQL superuser or pgreadserverfiles role can resolve absolute paths to files readable by the PostgreSQL OS user, while a non-superuser is limited to the source-stated PGDATA-relative scope. This vulnerability is fixed in 5.2.3.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Chartbrewto a version that resolves this vulnerability.Fixed in 5.2.3
Event History
Frequently Asked Questions
Who is exposed to this issue?
Exposure requires an AI-enabled PostgreSQL connection and a Chartbrew team Owner or Admin. The connected PostgreSQL role must also be able to invoke server-side file functions; the impact is greater for a PostgreSQL superuser or a role with pg_read_server_files.
Are default Chartbrew deployments affected?
The vulnerable path is not reachable unless AI features are enabled and an elevated Chartbrew user uses the AI query tool with PostgreSQL. Deployments without that combination are not exposed through the described surface.
What can an attacker do if exploitation succeeds?
Generated SQL can bypass the AI SQL-validation blocklist through unlisted sibling filesystem functions or double-quoted denied function names and reach PostgreSQL. A superuser or pg_read_server_files role can resolve absolute paths readable by the PostgreSQL OS user; non-superusers are limited to the stated PGDATA-relative scope.
What should be done if upgrading is not immediately possible?
Disable AI features or prevent Owners and Admins from using the AI query tool with PostgreSQL connections. Restrict the database role used by affected connections so it cannot call server-side file functions, particularly avoiding superuser and pg_read_server_files privileges.
Which version contains the fix?
The issue is fixed in Chartbrew 5.2.3.