# 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.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-4923-m569-jc42

## 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 (Improper Neutralization of Special Elements used in an SQL Command)

## 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.

## Is CVE-2026-61852 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61852 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61852 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61852 exists.

Affected product: chartbrew. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61852/ (Markdown: https://insights.sbomify.com/CVE-2026-61852/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61852
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61852
- OSV: https://osv.dev/vulnerability/CVE-2026-61852

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61852/
Summaries are generated and may contain mistakes; the official description above is the record.