External risk intelligence

Chartbrew API Connection Bypass Allows Internal Network Access

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-68935

Chartbrew is internet-facing, but this SSRF flaw requires an authenticated user with API management permissions. Because exploitation is restricted to authorized users rather than unauthenticated internet actors, direct exploitation of this configuration is less common.

Server-Side Request Forgery

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory describes a vulnerability in Chartbrew, an open-source application used for creating charts from data sources. The issue allows an authenticated user with specific permissions to potentially access internal network services from the Chartbrew server, which could lead to unauthorized actions or information disclosure.

  • Allows authorized users to access internal services.
  • Matters if Chartbrew connects to sensitive internal systems.
  • Confirm relevance and exposure to internal resources.

Attack Path

How an attacker could exploit the issue

An attacker with existing authenticated access to Chartbrew can manipulate API connection settings to target internal services. By enabling a specific field during API connection creation or update, the attacker bypasses network restrictions, allowing Chartbrew to send requests to any internal HTTP service accessible from its server. This could expose sensitive information or allow unauthorized actions on internal systems, though access to cloud metadata endpoints remains protected.

  • Requires authenticated user access.
  • Modifying API connection settings.
  • Access internal network services.

Live Threat

Current exploitation, exposure, and threat context

An authenticated user with API management permissions could manipulate Chartbrew's API connection settings to send requests to internal network services from the Chartbrew server. This could lead to the disclosure of sensitive information from internal systems or trigger unauthorized actions on those systems, when they are accessible to the Chartbrew server.

  • Internal HTTP services.
  • Authenticated user input allows bypassing restrictions.
  • Information disclosure or unauthorized actions.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Chartbrew application owner is responsible for addressing this vulnerability, as it impacts an open-source web application used for data visualization. The first practical step is to identify all Chartbrew instances, confirm their reachability and business criticality, and then locate the accountable owner to plan remediation.

  • Application owners should address this.
  • Verify Chartbrew instance reachability and criticality.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Chartbrew?

Chartbrew is an open-source web application designed to connect to various databases and APIs, allowing users to visualize that data through custom charts and dashboards. Organizations typically use it as a centralized tool to pull raw information from different business systems and display it in a user-friendly format.

What is the weakness behind CVE-2026-68935?

This vulnerability is a Server-Side Request Forgery (SSRF), classified as CWE-918. It occurs when an application can be tricked into sending requests to locations it should not access. In this case, the software allows users to override security settings that are intended to prevent the server from interacting with private, internal network services.

How can an attacker trigger this vulnerability?

An authenticated user with permission to manage API connections must intentionally enable the internal 'allowPrivateHost' field when creating or updating a connection. Simply disabling the global network settings for the instance is insufficient because the individual connection override takes precedence. This flaw does not apply to cloud metadata endpoints, which remain restricted.

Is my instance at risk according to Halo Surface Signal?

While Chartbrew is typically internet-facing, Halo Surface Signal notes that this vulnerability requires an authenticated user with existing API management permissions. Because a malicious actor must already have authorized access to your internal system, the likelihood of outside, unauthenticated actors exploiting this configuration directly is lower than in other attack scenarios.

What should I do to secure my Chartbrew installation?

The primary step is to upgrade your Chartbrew software to version 5.2.3, which contains the fix for this issue. You should also audit your current API connections to ensure the 'allowPrivateHost' setting is not enabled and review the permissions of users who have access to manage those connection configurations.

References