CVE-2026-68935 · Package
NO FIX YET · SEE WHAT TO DO
Chartbrew, a self-hosted charting app, lets an authenticated user set an internal allowPrivateHost flag on API connections, which an upgrade migration also turns on for existing connections. Successful exploitation lets requests reach internal HTTP services reachable from the Chartbrew server, possibly disclosing data or triggering unauthorized actions.
first public Sep 20, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running self-hosted Chartbrew versions 4.8.5 through 5.2.2 where users can create or edit API connections. The upgrade migration enables the override on existing connections, so disabling the instance-wide setting does not protect them. Instances on 5.2.3 or later, or without authenticated users who can manage API connections, are less exposed.
Not affected if auth-required, patched-version
Who cares chartbrew, internal-network, self-hosted
4.8.5 through 5.2.2 are in the affected range.CB_ALLOW_PRIVATE_NETWORK_CALLS is set, since the per-connection override takes precedence over it.5.2.3.Chartbrew is an open-source web application for creating charts from databases and APIs. In versions 4.8.5 through 5.2.2, API connection creation and update operations accept the internal allowPrivateHost field from user input. An authenticated user with permission to manage API connections can enable this field to bypass private and reserved-network destination restrictions. An upgrade migration also enables the override on pre-existing API connections. The per-connection setting takes precedence over CB_ALLOW_PRIVATE_NETWORK_CALLS , so disabling that instance option does not protect connections with the override enabled. Successful exploitation allows requests to internal HTTP services reachable from the Chartbrew server, potentially disclosing information or triggering unauthorized actions depending on the target service. Recognized cloud metadata endpoints remain separately blocked. This issue is fixed in version 5.2.3.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.