Quick answers
- Is CVE-2026-69128 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-69128 being exploited in the wild.
- How severe is CVE-2026-69128?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- Chartbrew 5.2.2.
- Is there a fix for CVE-2026-69128?
- Yes: fixed in 5.2.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-69128 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-69128?
- Check whether you run Chartbrew at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 5.2.3
Technical details
The vulnerability exists in the AI query tool's SQL blocklist for PostgreSQL, which used incomplete regular expressions that missed both sibling filesystem functions (pg_stat_file, pg_ls_logdir, etc.) and double-quoted identifier forms of blocked functions (e.g., "pg_read_file"()). An attacker with Owner or Admin privileges who can enable AI features on a PostgreSQL connection can craft queries using these bypasses to invoke file-reading functions, potentially reading files readable by the PostgreSQL OS user account. The fix consolidates the blocklist into a single family-prefix pattern that covers all pg_read*, pg_stat*, pg_ls*, and pg_current_logfile variants with optional quote-matching.
Affected products
- Chartbrew Chartbrew 5.2.2
Timeline
- 2026-11-06: disclosed
- 2026-07-19: patched: Release v5.2.3